API Users Group News

Subscribe to API Users Group News feed
Group to facilitate communication with and between those using the ORCID APIs
Updated: 18 min 18 sec ago

Scheduled outage on Saturday 15 December

Mon, 16 Jul 2018 - 16:04 UTC
On Saturday, December 15, ORCID will be migrating our database to new hardware. During this transition the ORCID Registry, including the Public and Member APIs and the ORCID Registry user interface, will be unavailable for up to four hours. An additional reminder with the specific time of the

Client not found error whenever I try to get an auth token

Sat, 23 Jun 2018 - 13:33 UTC
So... I went through your bizzare auth ritual, got a code and then tried to get an auth token (**this seems over-engineered as fuck, I mean, a simple auth credentials header will do, it's not a stock broker or bankl it's just some administrative data). In any case, I get the following error:

Problem with sandbox signin?

Mon, 21 May 2018 - 15:04 UTC
I'm working on code to talk with the sandbox, going through the usual 3-legged authentication to get and confirm data. Today, on the usual signin link, the link goes to unsafe:javascript:void(0); which unsurprisingly doesn't work, at least in Firefox. Any more info about this? Many thanks,

one-time-only permissions?

Thu, 17 May 2018 - 17:26 UTC
Please forgive me if I "missed the memo". I returned to developing code against the sandbox today, and saw that the "grant authorization" screen no longer offers a checkbox for "Allow this permission until I revoke it." (screen shot attached). Is this: 1) Something I should have known about? 2)

How to create automated authentication mechanism for OrcID on bash console.

Wed, 16 May 2018 - 08:27 UTC
I want to do authentication process from using console. Is it possible? I have followed this guide (https://members.orcid.org/api/oauth/3legged-oauth). First issue I was not able to obtain code=**** through console, is there any script that I can use. Imagine: user provide me their client_id

Re: [ORCID API] Generate a two step (read-public): "error":"invalid_client","error_description":"Client not found:

Mon, 07 May 2018 - 14:12 UTC
Hi, The client iD that is returned in your error message (APP-90R3NMFJNN5M4J84) is for the ORCID production environment at orcid.org, but the call you provided is for our sandbox at sandbox.orcid.org. (More about the sandbox is at https://support.orcid.org/knowledgebase/articles/166623-is-the-

Generate a two step (read-public) access token:"error":"invalid_client","error_description":"Client

Mon, 07 May 2018 - 14:04 UTC
I am following up this thread. I have followed ( https://github.com/ORCID/ORCID-Source/tree/master/orcid-api-web#generate-a-two-step-read-public-access-token ) I have tried with my `Client ID` and` Client secret` curl -i -L -H 'Accept: application/json' -d > 'client_id=APP-674MCQQR985VZZQ2' -d >

OpenID 'sub' change schduled for May 16th

Thu, 19 Apr 2018 - 10:22 UTC
All, We have scheduled the change to the format of the 'sub' element within id_tokens for the 16th of May. This is to address the following issue: There is a mismatch between the 'sub' provided within our OpenID tokens and the 'sub' provided by the userinfo endpoint. Specifically, the

Members report - analysis

Tue, 17 Apr 2018 - 14:12 UTC
Not strictly an API question - for those that are member organisations of ORCID, have any of you used the member reports to carry out any further analysis? We have a member organisation (in the UK consortium) that would like to generate some graphs (or similar) based on the figures in the

are credentials, tokens, authentication needed for obtaining personal information from an ORCID?

Wed, 11 Apr 2018 - 14:30 UTC
I have a very simple use case in which all I need to do is to obtain the first and last name of a researcher given their ORCID. My system will not use ORCID for authentication / single sign-on purposes as we have our own authentication system. I am trying to navigate the bloated, buggy, visually

OpenID 'sub' mismatch.

Mon, 09 Apr 2018 - 11:35 UTC
All, It's been brought to our attention that there is a mismatch between the 'sub' provided within our OpenID tokens and the 'sub' provided by the userinfo endpoint. Specifically, the id_token contains https://orcid.org/0000-0000-0000-0000 but the user info contains 0000-0000-0000-0000. We