As we continue to develop our products, there are a number of features that are only available with API 3.0 which is our latest and default API version. The table below provides a short description of each feature. If you have any questions regarding any of the features or upgrading to 3.0 then please reach Continue Reading
ORICD API
Do you have an API version policy?
Yes we do! You can read more about our API versioning, the rationale behind it and more, here at our API Version Policy. Was this helpful?Yes NoAdditional Comments:Send Feedback
How do I get a ‘webhook’ access token?
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
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