#Have some rest synonym update

Continuing with the last example above, let’s examine the structure of the URL, which is divided into the three main parts of input, operation, and output, in an ordered sequence that will sometimes be referred to in this document as the URL path: PUG REST is entirely based on HTTP (or HTTPS) requests, and most of the details of the request are encoded directly in the URL path – which is what makes the service RESTful (informally anyway, as it does not adhere strictly to REST principles, which are beyond the scope of this discussion). And at the same time, more complex data handling is available for programmers who want rigorous schema-based XML communications, or who want to use JSON data to embed functionality in a web page via JavaScript. The possibilities are nearly endless, and more importantly, the action of the service is simple to understand from the URL alone, without needing any extra programming, XML parsing, etc. Or, combine input by chemical name with InChI property retrieval, and you have a simple name-to-InChI service in a single request: You can combine these two into a visualization request for a SMILES string – in this case, whether or not that particular chemical is even in the PubChem database at all! And it’s something you can almost type manually into a web browser: It supports output of chemical structure as images in PNG format. So instead of a list of separate narrowly defined service requests that are supported, you can combine these building blocks in many ways to create customized requests.įor example, this service supports input of chemical structure by SMILES. Meaning that, for example, any form of input that specifies some group of CIDs can be combined with any operation that deals with CIDs, and any output format that’s relevant to the chosen operation. The beauty of this design is that each of these three parts of the request is (mostly) independent, allowing a combinatorial expansion of the things you can do in a single request. The conceptual framework of this service, that uses these identifiers, is the three-part request: 1) input – that is, what identifiers are we talking about 2) operation – what to do with those identifiers and 3) output – what information should be returned. The fundamental unit upon which PUG REST is built is the PubChem identifier, which comes in three flavors – SID for substances, CID for compounds, and AID for assays. List sharing between PUG-REST and E-Utilities If you have a large data set that you need to compute with, please contact us for help on optimizing your task, as there are likely more efficient ways to approach such bulk queries.Īccess to PubChem Substances and Compounds To check additional request volume limitations, please read this document. We ask that any script or application not make more than 5 requests per second, in order to avoid overloading the PubChem servers. For comments, help, or to suggest new functionality or topics for this tutorial, please contact POLICY: Please note that PUG REST is not designed for very large volumes (millions) of requests. PUG REST is actively maintained and updated, so check this page for new features. Users may also be interested in PUG View ( ), which provides more complete but longer summary reports on individual PubChem records. PUG REST is mainly designed to give small bits of information on one or more PubChem records. PUG SOAP, for applications that have built-in SOAP handlers, or programming languages with an API generated from a SOAP WSDL:.A more technical and complete PUG REST specification document, but that is a little harder to read:.Some other documents that may be useful are: Chemical Biology Informatics and Modeling. Programmatic Retrieval of Small Molecule Information from PubChem Using PUG-REST. PUG-SOAP and PUG-REST: web services for programmatic access to chemical information in PubChem. Kim S, Thiessen PA, Bolton EE, Bryant SH.

#Have some rest synonym update

An update on PUG-REST: RESTful interface for programmatic access to PubChem. Kim S, Thiessen PA, Cheng T, Yu B, Bolton EE.