Integrations need to store more than just ORCID records. Your system will need to be able to:
Accept and store ORCID iDs: Your system will need to know the iD of the ORCID record to update. Store it together with the researcher's information. Our recommendation is to store the full https URI: https://orcid.org/0000-0001-5727-2427.
Accept and store persistent access tokens and refresh tokens: Access tokens can be used to read and update records, as well as indicate that the iD has been authenticated. Persistent tokens are valid for approximately 20 years or until the user revokes them. Refresh tokens can be used to create new access tokens with the same or limited scopes. Store the tokens together with the researcher's information. We also recommend you store the token scope, and the‚token expiry.
Accept and store put codes (if updating ORCID records): Every item that you add to the ORCID Registry will be returned with a put code by the ORCID API. Save this put code along with the item in your system‚ it's how you‚ll identify which item needs to be read or updated.
Log interactions: Your system should record both calls made to the ORCID API and responses received. This is necessary so ORCID can help if a problem develops later.
Provide error messages and a support contact when an interaction does not go as expected.