ZINC api: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Here we explain how to access ZINC programmatically. Currently, there are a number of pages on this topic, which we intend to re-write in a more formal way. | Here we explain how to access ZINC programmatically. Currently, there are a number of pages on this topic, which we intend to re-write in a more formal way. | ||
* [[ZINC Command | * [[ZINC:Command language]] - RESTful API to many ZINC objects and functions | ||
* | * | ||
Revision as of 13:32, 1 May 2014
Here we explain how to access ZINC programmatically. Currently, there are a number of pages on this topic, which we intend to re-write in a more formal way.
- ZINC:Command language - RESTful API to many ZINC objects and functions
ZINC api (r/w)
models defines tables, what columns they have, relationships
managers defines higher-level common queries
The ZINC api is composed of many managers (one for substances, one for catalogs, one for targets, etc)
You can do things like this with a manager:
in_stock = zinc.catalogs.query(Catalog.purchasbility==1)