All items (apart from the biography text) on an ORCID record have a put code: This put code can be used to make a call to the API to retrieve […]

A list of common API error codes, their possible meanings and tips on how to troubleshoot them is available within our technical documentation. If you are not able to resolve […]

ORCID members can update information they’ve previously added to an ORCID record. Only one item can be updated at a time, and it can only be updated using the client […]

Items (works, employment, funding, peer review etc) can be added to an ORCID record using the ORCID member API. To do this, you must first obtain permission from the researcher […]

Visibility indicates the privacy setting of the item, based on the user’s set visibility preference. If a visibility tag is included when information is posted via the API, it will […]

If you have added data that needs to be deleted, for example, if it has been associated with the wrong ORCID iD, then you can make an HTTP DELETE request […]

The ORCID search API uses the SOLR syntax. All query syntaxes available in SOLR 3.6 are supported, including Lucene with Solr extensions (default), DisMax, and Extended Dismax. You need a “/read-public” […]

The ORCID search API uses the SOLR syntax. All query syntaxes available in SOLR 3.6 are supported, including Lucene with Solr extensions (default), DisMax, and Extended Dismax. You can use a fielded […]

In real-world situations, API interactions are completed by your system using a programming language such as PHP, Java, or Ruby on Rails. For practice and testing, you can interact with […]

Webhooks can be registered by premium members against any ORCID record in the registry. The steps are: Encode the URL URL-encode the URL that you want ORCID to call when […]