An example call to get an authorization code is below.This example can be pasted directly into your web browser -- be sure to first replace with your own client ID and redirect URI.

updating bio-48

curl -i -L -H "Accept: application/json" --data "client_id=APP-NPXKK6HFN6TJ4YYI&client_secret=060c36f2-cce2-4f74-bde0-a17d8bb30a97&grant_type=authorization_code&code=w7oay3&redirect_uri=https://developers.google.com/oauthplayground" "https://sandbox.orcid.org/oauth/token" HTTP/1.1 200 OK ...

{"access_token":"aa2c8730-07af-4ac6-bfec-fb22c0987348","token_type":"bearer","expires_in":631138518,"scope":"/orcid-bio/update","orcid":"0000-0002-2389-8429","name":"Sofia Hernandez"}As the PUT function will overwrite existing biographical information in the profile that you have added, you must first GET the existing biographical information to edit it.

With the above access token you will be able to return both public and read-limited information.

This tutorial will walk you through updating biographical information in an ORCID record using the PUT commands in c URL.

Note that using PUT updates all information and will replace the existing biographical information in a researcher’s record that you have added.

(You will be unable to edit or replace any information which you did not add.) The text in bold in each example should be replaced with your own credentials, ORCID i D, and system responses.The XML used in the orcid-bio section is described at XML for ORCID Bio.Updating biographical information follows the OAuth dance as described in Tokens Through 3-legged OAuth Authorization.The access tokens can be short-lived (expiring one hour after issue) or long-lived (expiring 20 years after issue).Either type of token can be used multiple times before it expires.Putting biographical information uses the scope /orcid-bio/update.