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.
API News & Updates
As of April 13th any members using the 2.0 release candidate schema will be required to use https in calls to the ORCID API. In calls to post to, put to, or read ORCID records the URL must start with https. For example when reading the activities on a record the URL is https://api.orcid.org/v2.0_
We wanted to let you know about changes we’re making to the identifier field in the works and funding section of the ORCID schema version 2.0_rc1. This change does not impact existing integrations using schema version 1.2.
We’re making a couple changes to the OAuth workflow which will improve the workflow for site using ORCID sign in for authentication.
If an active access token already exists with the same scopes and the user is logged into their ORCID record, they will not be prompted to grant authorization again. Instead they will be taken directly to the redirect URI.