Update: https://0-api-crossref-org.lib.rivier.edu/works/10.51415/ajims.v4i1.954 now retrieves the record, but there are others, such as https://0-api-crossref-org.lib.rivier.edu/works/10.51415/ajims.v4i1.953, still with ‘Resource not found.’
Maybe I just need to wait a couple of days? Still, it seems weird to me that a DOI can resolve yet not be retrievable through the API.
You haven’t done anything wrong! The problem is on our end.
The process which indexes registered DOIs in the REST API has been intermittently struggling lately. The missing DOIs are registered (i.e. they resolve at the handle, as you’ve seen) and they are indexed in our older, XML API. But, they’re not making it into the REST API or any of its derivative services.
Our technical team is aware of the problem and investigating.
If you send us an email at email@example.com with any DOIs that you get that “resource not found” for in the REST API, we’ll ask one of our developers to re-push them for indexing.