API News & Updates

XSD 2.0 update

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 sunset on the public API on March 1, 2017, and on the member API on August 1, 2018.

This article describes this update and outlines changes that API users will need to put in place.

API version 2.0_rc3 released

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.

Https required for version 2.0

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_rc1/0000-0001-5109-3700/activities. This applies to both the member and public API.

Updates to identifiers for activities

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.