We are delighted to announce that the latest version of our API, version 2.1, is now live. This version fully supports the canonical form of the ORCID iD: https://orcid.org/0000-0002-1825-0097. The launch of API 2.1, which makes HTTPS ORCID iDs supported in the Registry, helps us as we strive to build a reliable Registry that secures your information and protects against vulnerabilities. There are no other functional changes to API calls or the XSD in this release.
What do I need to do?
If you’ve already upgraded to 2.0 or are in the process of doing so, no action is needed as we will continue to support both 2.0 and 2.1 for the foreseeable future. If you’re interested in moving to 2.1 in order to benefit from HTTPS ORCID iDs, please contact us.
If you are currently developing an ORCID integration, we encourage, but do not require, you to develop using API 2.1 to enable your workflows to benefit from HTTPS ORCID iDs.
If you are already displaying ORCID iDs, we recommend that you switch to the HTTPS version of the ORCID iD. See our updated Trademark and iD Display Guidelines.
If you haven’t yet started your ORCID integration, we encourage you to do so using API 2.1.
Please note that display of HTTPS ORCID iDs will be required to meet the Display element of our Collect & Connect program from 2018 onward. See our updated API documentation.
For more information, please see The Canonical Form of the ORCID iD Is Coming and, if you have any questions, please contact us.
