Adobe Places Increase Maximum Limit for Number of Responses in API Call

[jerrodabee]

When I fetch a list of POIs in our Adobe Places API call in a particular library, there are 128 values, but the response is only sending 100.  Through looking in previous questions, I see that this problem has been raised, and solved using a mix of the "start" and "order by" query parameters: Solved: Re: Increase maximum limit for number of objects f... - Adobe Experience League Community - ...

However, the "start" query parameter is not changing the starting point of returned values for this API.  I am utilizing the Postman integration to pull from the API, and so I am able to set the parameter "orderby" ascending and descending to grab all of the libraries values, but this is horribly inefficient.  Is there a query parameter for the Adobe Places API that I am missing? Am I incorrectly using the query parameters? 

For reference, these two requests (with the appropriate header IDs) return the exact same values: 

https://api-places.adobe.io/places/placesapi/v1/libraries/<libraryID>/pois?start=1&limit=10&orderby=name 

https://api-places.adobe.io/places/placesapi/v1/libraries/<libraryID>/pois?start=10&limit=10&orderby=name

[AmitVishwakarma]

Hi @jerrodabee ,

Use Manual Pagination with orderby and Track the last item in Each Batch

Since start is not functioning as true pagination, you need to implement manual pagination using the orderby parameter and the value of the last returned POI in each request to fetch the next batch.

Try below steps:

1. Set your limit to 100 (max allowed):

https://api-places.adobe.io/places/placesapi/v1/libraries/<libraryID>/pois?limit=100&orderby=name

2. Capture the last item's name (or whatever field you use for ordering).

3. Use orderby=name and filter to fetch next batch:

Adobe Places API does not support start well, so you simulate pagination like this:

https://api-places.adobe.io/places/placesapi/v1/libraries/<libraryID>/pois?limit=100&orderby=name&filter=name>lastName

Replace lastName with the name of the last POI from the previous batch.
Repeat this process until you’ve retrieved all POIs.

Automate with Postman (Optional)

Use Postman’s Tests tab to store the last item's name in a variable, and use it in the next request’s filter param, looping through all batches.

Note:

Ensure you url-encode special characters in the filter (e.g., &, spaces).

This technique works best with unique sortable fields like name, id, or createdAt.

Regards,
Amit

[jerrodabee · Accepted solution]

Hello Amit, 

Thank you for the guidance! I unfortunately was not able to simulate the pagination through Postman using the filter query parameters.  However, I was able to simulate the pagination by using the "page" query parameter.  So, while ordering by "name" I set the "limit" to 100 and the "page" to 2 and was able to capture the second page of data.  

Thank you very much! 

[AmitVishwakarma]

Hi @jerrodabee ,

Thanks for the update — glad to hear you were able to get pagination working using the page parameter!

Regards,
Amit