Register a member API client application

This article has been superseded by https://info.orcid.org/documentation/integration-guide/registering-a-member-api-client/ 

Before you can use ORCID's Member API, need to create an API client which will give you login credentials for your application: a Client ID (consumer KEY) and Client Secret (consumer SECRET). Your application will use these credentials as it interacts with the ORCID API.

To obtain client application credentials for the Member API on the production site, you first will need to become an ORCID Member.

However, anyone can try the member API on the ORCID sandbox testing server. To do so, you will register a client application following the instructions below. (Note that this process is not automated and your reply may take up to a couple days to process.)

To get started, fill in the form to register a client application. Below is a quick overview of the requested fields:

Display name and description displayed to users on the authorization page

Display name and website displayed under trusted organizations

Once you have made your request, a manual process happens to issue you credentials and you will get an email with your client iD and client secret. Typically these requests are process in less than 24 hours.

Some larger organizations can have 100s or 1000s of potential callback URIs. In these situations it can sometimes be impractical to register all of them. There are several approaches one could take to manage high numbers of Callback URIs:

About Redirect URIs

1. Register no redirect_uris at all (Sandbox only)

If the client app is configured with no redirect_uris, then any redirect_uri can be used. This is less secure than specifying redirect_uris. The redirect_uris give an extra level of security because they prevent somebody using someone else's stolen client credentials (because we would never redirect to their domain - they would also have to have control over the user's DNS to get round that!). For more on the potential risks here, you may enjoy this short post staring "Evil User": OAuth 2.0 Redirection URI Validation.

2. Register just the host name

If the client app is registered with a redirect_uri that is just the host name, then any redirect_uri at that host can be used. So, for example if the following redirect_uri is registered

https://thirdparty.com

then all of the following redirect_uris will work

https://thirdparty.com/oauth/callback1

https://thirdparty.com/callback2

https://thirdparty.com/anything-else-as-long-as-the-host-is-the-same

If they need https as well, then that needs to be registered separately. Also, sub domains need to be registered separately, e.g. http://app.thirdparty.com.

NOTE: If you decide that this approach might work for you - you can perhaps handle the URIs by registering all of the redirect URIs in one of your domains and then redirect again to the appropriate domain.

3. Register all redirect_uris fully

This method is encouraged when practical.

All redirect URIs must start with the https prefix on the production server, while http is allowed for testing on the sandbox server. Localhost can be registered as a redirect URI using http://localhost (for Sandbox server only).