DOI missing from polite REST API

Metadata Retrieval Interfaces for Machines
,
1

DOI 10.1039/D2CP01254E is missing from the polite REST API but available from the public one.

Using content negotiation against the public API returns a 200 OK response. When adding our email address to the User-Agent to access the polite API, the response is a 404 Not Found.

API endpoint that we’re calling is:
api[dot]crossref[dot]org/v1/works/10.1039%2FD2CP01254E/transform

1 Like
2

Hi @mpaluch ,

Thanks for your post, and welcome to the community forum. This DOI has been registered with us and is available in our XML API, as you can see here: https://0-doi-crossref-org.libus.csd.mu.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1039%2FD2CP01254E

We do have a bug in the way in which some new DOIs are indexed in the REST API. That bug has resulted in this DOI from missing from the REST API. I have asked our technical team to re-push this DOI so it can be indexed. You may follow our progress here: [CR-532] - Jira.

I’ll also follow up here when I have an update.

More as I have it,
Isaac

3

Hi Isaac,

the DOI 10.1038/s41564-022-01157-1 seems missing too. Could it be linked to the same problem ?

Thanks,
Fred

1 Like
4

Hi @fmerceur ,

Yes, that looks to be the same issue. Thanks for reporting it, Fred. I have reported to our technical team for fixing. The metadata record is present in our XML API, if you need an alternative to the REST API while we get this sorted: http://0-doi-crossref-org.libus.csd.mu.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1038%2Fs41564-022-01157-1

-Isaac

5

Hi @fmerceur ,

DOI 10.1038/s41564-022-01157-1 is now present in our REST API https://0-api-crossref-org.libus.csd.mu.edu/works/10.1038/s41564-022-01157-1 and search interface: https://0-search-crossref-org.libus.csd.mu.edu/?q=10.1038%2Fs41564-022-01157-1&from_ui=yes.

Kind regards,
Isaac