This announcement is to inform you that we’re changing the behavior when you attempt to exchange a single authorization code multiple times. Currently when an authorization code is exchanged the first time we return an access token, if the authorization code is used again we return an error message but take no action on the token. With this update, on the second exchange we’ll continue to return an error message but will also revoke the token that was generated on the first exchange.
API News & Updates
Recently we have been making several changes to improve the ORCID API; one is standardizing the url used during the token exchange so it is the same on both the Public and Member API, and ending support for api-specific urls.
We announced to members and users in late March that a verified email address will be required to access all the features on the user interface of ORCID records. The requirement went live on April 20, 2017.
XSD 2.0 is now available on the production ORCID Registry and sandbox as a stable release version. On February 14 we will update the default ORCID Message Schema from v1.2 to v2.0, and we will no longer support v1.2 or release candidates of v2.0. v1.2 will sunset on the public API on March 1, 2017, and is expected to be sunset on the member API in 2018.
This article describes this update and outlines changes that API users will need to put in place.
API version 2.0_rc3 is now available for testing on production and sandbox (it was previously available on sandbox, but a few changes have been made since then). With rc3, members are able to bulk post up to 100 works with one call. We request that all members interested in bulk loading works test on the sandbox first to ensure any issues with load on the API are discovered there, rather than on production.