Paging

To limit server memory/CPU consumption, the API performs paging of results. By default, only 100 results will be returned per query/page.

You will see evidence of this in all "list" API views, where the data will be structured something like

{
    "count": 1031,
    "next": "https://deploy.c1engineering.com/api/projects/endpoint/?limit=100&offset=100",
    "previous": null,
    "results": [
        {
            "Attributes": "Here"
        }
    ]
}

In the above example, you can see the total result count, the URLs you can use to view the next / previous pages, and the actual objects in the results array/list.

The next and previous page URLs probably give you a clue about how to tweak with the paging settings using query parameters.

For example, you can return more than 100 results per page by providing a limit query parameter.

To return up to 250 locations, we can query the URI:

Return up to 250 results per page

/api/projects/locations/?limit=250

To iterate through the pages, you increment the offset parameter by adding the limit to it which will return the next page of results.