Pagination and API data
How to manage large data set responses for efficiency and manageability.
The NetSapiens API supports pagination in most of the endpoints detailed in the API reference. Effectively, every GET method that isn't a count of some kind will support START and LIMIT parameters in your queries.
NOTE: these parameters should NOT be applied to GETs for a specific singular datum. That is to say, this type of data filtering is only applicable to API calls which do NOT return a single object/resource, a count of an object/resource, or a list object with an array of associated data.
Also, the easiest way to use pagination in this sense would be to set a LIMIT of '1', and then increment the START value to test the output.
Here's an example of what we're talking about here:
GET https://dev1.ns-api.com/ns-api/v2/domains?start=1&limit=100
To view the next 100 records, you would increment the START value to the start of your next set, such as '101' in the example above when using a LIMIT of 100.
Updated 3 days ago