# REST API retrieves incomplete list of registered submissions

**URL:** <https://community.crossref.org/t/rest-api-retrieves-incomplete-list-of-registered-submissions/2726>\
**Category:** Technical Support\
**Tags:** rest-api, metadata-retrieval\
**Created:** [2 June 2022 11:47 UTC](https://community.crossref.org/t/rest-api-retrieves-incomplete-list-of-registered-submissions/2726 "2022-06-02T11:47:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![seanc](https://avatars.discourse-cdn.com/v4/letter/s/ad7895/32.png) [@seanc](https://community.crossref.org/u/seanc)\
**Post date:** [2 June 2022 11:47 UTC](https://community.crossref.org/t/rest-api-retrieves-incomplete-list-of-registered-submissions/2726/1 "2022-06-02T11:47:37Z")

</div>

I’m trying to generate a list of all registered submissions using the REST API, but don’t seem to be retrieving a complete list.

I use:

`https://api.crossref.org/prefixes/10.51415/works?select=DOI&rows=1000`  
and  
`https://api.crossref.org/prefixes/10.51415/works?&select=DOI&rows=1000&offset=1000`

This gives me all 1991 results: “total-results”: 1991.

However, omitted from these results are several DOIs that are registered and do resolve, including: 10.51415/ajims.v4i1.954

And I get ‘resource not found’ for:

`https://api.crossref.org/works/10.51415/ajims.v4i1.954`

Yet, `https://doi.org/10.51415/ajims.v4i1.954` resolves.

I don’t know where I’ve gone wrong.

---

<div class="post-metadata">

**Author:** ![seanc](https://avatars.discourse-cdn.com/v4/letter/s/ad7895/32.png) [@seanc](https://community.crossref.org/u/seanc)\
**Post date:** [2 June 2022 12:50 UTC](https://community.crossref.org/t/rest-api-retrieves-incomplete-list-of-registered-submissions/2726/2 "2022-06-02T12:50:03Z")

</div>

Update:  
`https://api.crossref.org/works/10.51415/ajims.v4i1.954` now retrieves the record, but there are others, such as `https://api.crossref.org/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.

---

<div class="post-metadata">

**Author:** ![Shayn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/shayn/32/57_2.png) [@Shayn](https://community.crossref.org/u/Shayn)\
**Post date:** [2 June 2022 13:14 UTC](https://community.crossref.org/t/rest-api-retrieves-incomplete-list-of-registered-submissions/2726/3 "2022-06-02T13:14:56Z")

</div>

Hi,

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 [support@crossref.org](mailto:support@crossref.org) 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.

Apologies for the inconvenience.

-Shayn