Hi Ailish,
AtoM's API endpoints can certainly be improved upon - the application is not really API driven, so they were added later on and aren't as fully featured as they might be. That said, perhaps the documentation will help:
As noted in this section, the limit of records returned in the response is controlled by AtoM's global results per page setting. You could ask your client to increase this to return more results - though we don't recommend setting it too high, or the response may time out before completing. Try 50 results and see how that goes. Here's a link to the setting, which you could pass on to your client:
Knowing that there are a specific number of results returned in a single response means you can use the skip parameter in your query to page to the next set. From the docs:
- skip: The amount of information objects skipped when returning the results. This parameter can be used to page results - for example, if the first response includes 10 results, then the following request can include a skip=10 parameter, which will skip the first 10 results and begin the response on the 11th. See the examples below.
- Example - Skip the first 20 results: /api/informationobjects?skip=20
Hope this helps!
Regards,