Web services
The GPCRmd API is oriented to facilitate to users to acces to the information of GPCRmd database more efficienty and fastest using coding and urls. Behind this tool we used the framework django-rest with the updated Swagger version under the name of drf_yasg.
As it can be observe in the image above, the api is divided into two sections:
Main GPCRmd API: list of tools to obtain data from the GPCRmd database.
Other GPCRmd API: group of tools related with the obtain of files from GPCRmd, like structures. Note: this group of tools need an account on GPCRmd.
Main GPCRmd API
This part of the API is related with the data stored in the GPCRmd database. Here, the user can found functions from retrieve all pdbs on GPCRmd to retrieve the dynamics associated to a list of Uniprot codes:
All the functions are GET functions but mainly, there are two types of functions: without input parameters or with them.
For one side, the functions without the need to use a parameter as input, like search_all_pdbs, the user only need to click on “Try out” and then on “Execute”.
Next, the server will process the request of the user retrieving the result. In the example case of search_all_pdbs, the response is a json with all the codes PDB stored in GPCRmd.
Note
The user can download this json using the “Download” button on the bottom or use the url to obtain directly the json.
For the other side, the functions with the need of an input, like search_dyn, when it is click on “Try out” the web display the input parameters necessaries to retrieve the information from GPCRmd.
Once the response is recived, the user can see the json with all the information requested.
Note
In case that the user use as input a list of elements separated by comma, the api will return a json with multiple elements.
Other GPCRmd API
This other part of the api is related with the files stored into GPCRmd.
API Downloader
For security, to have a control of who’s is downloading the data from the web it is necessary to be log in with a GPCRmd account (see GPCRmd account guide).
One of the functions is the downloader. The main function of this tool is to download all the files related to a dynamic, from topology to protocol files.
Warning
To protect server performance, downloads are limited to 5 dynamics ids per request, and to a weekly quota per user. Your current quota usage is shown above the request form.
Weekly quota
Each user account has a limit of 10 dynamics that can be downloaded per week through this tool. The counter resets every Monday. You can see how much of your quota you’ve used at the top of the downloader, next to the request form.
If you reach your weekly limit, new download requests will be rejected until the quota resets. Dynamics from a failed or incomplete download do not count against your quota — only successfully completed downloads are counted.
If you need a higher limit for a specific research need, please contact us at info@gpcrmd.org.
This process take some minutes because there are large files to collect, compressed and retrieve to the user. Let it run on the background. If you reload the page while a download is running, the tool will automatically reconnect to your ongoing request and resume showing its progress — you don’t need to start it again.
Retrieving your download
Once the compressed file is created the user can see a button named “Download” to start the download of the file:
Each dynamic has its own directory, named after its id. Inside each directory you can find all the files related to that dynamic.
Alongside the download link, a Log file button becomes available, listing every file included in your download and any dynamics that could not be added (for example, if not yet published). It opens in a new tab so you can keep the download page open.
In case that you found any problem, do not doubt on contact us to info@gpcrmd.org.