The 3decision API allows to programmatically send requests to 3decision by using endpoints.
The API documentation describes how to access the 3decision API and how to use endpoints.
To help you use the API with Python, code snippets are also provided.
The 3decision API is reachable from a link that is unique to each Customer, and that has this format:
https://3decision-<customer>-api.discngine.cloud/full/
Where <customer> is an abbreviation of your company name, as indicated in the 3decision URL.
The URL https://3decision-<customer>.discngine.cloud will be used as an example in this API documentation.
If you don’t know what URL to use, please ask your 3decision admin or contact 3decision-support@discngine.com
The default rate limit for 3decision API endpoints is 250 calls per minute. Certain endpoints have a different limitation due to their specificities (for instance: interaction search endpoint can be long). In that case, the rate limit is indicated in the endpoint description in the API description (swagger).
Once the rate limit is reached, calling the endpoint returns a 429 error.
This section is intended for users not familiar with the swagger interface endpoint methods. Here is a short overview of the methods used by the endpoints available in the 3decision API.
Here is a short description of some of the terms used in the database:
| Name | Description | Format |
|---|---|---|
external_code |
UI structure identifier | For public structures: 4 letter PDB code. For internal structures: six letter alphanumeric code. |
structure_id |
database structure identifier | number |
small_mol_id |
database ligand identifier | number |
small_mol_conf_id |
database ligand conformation identifier | number |