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
ORICD API
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
Can I explore the ORCID API with Google OAuth Playground?
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, however, you can interact with the ORCID API using a range of tools capable of making and receiving HTTP requests. Most desktop HTTP tools (such as cURL) are run in Continue Reading