Anyone premium member can obtain a ‘/webhook’ access token. A single token can be used to register webhooks for multiple records.To obtain a token, you make a call to the ORCID API token endpoint. This process is often referred to as the client-credentials OAuth flow, or 2-step OAuth. Below is an example call to obtain Continue Reading
ORICD API
Sunsetting API Version 2
API 3.0 is the default API version and we recommend that when building new integrations that you use this version. We will continue to support API 2.0 and 2.1 for the foreseeable future, and will provide at least 12 months notice before switching off those versions. We learned a lot during the transition from API Continue Reading
Why Can’t I Read all Email Addresses?
Researcher control is a core ORCID principle, so email addresses registered and added to the ORCID record are, by default, set as only visible to the record holder. Unverified emails do not display in the public view of the record and only email addresses that have been verified will appear in API results. Once researchers have Continue Reading
What are the API limits?
For our API version 2.0 and above the limits are: Request a second – 24Burst – 40 Request a second – Number of request that can be made a second. Burst – Number of request we will allow to be queued before rejecting. Requests in the queue are slowed down to the rate of requests Continue Reading
Does ORCID support Schema.org, linked open data and JSON-LD?
The ORCID registry supports “content negotiation”. This means machines and other systems can ask ORCID registry for person metadata in different formats. One of these formats is JSON-LD, which uses the schema.org vocabulary, specifically the Person type, which we connect with works, organisations and other identifiers. We also support XML, JSON, RDF XML and turtle, Continue Reading