Skip to main content
List endpoints return one page at a time. Three patterns are in use. Pick the one that matches the endpoint you are calling.

Offset lists

GET /api/v1/psd-mockups and GET /api/v1/photo-mockups take limit and offset. limit defaults to 20 and accepts up to 100.
The two endpoints report the same three counters in different places. PSD mockups keep them inside data, photo mockups keep them at the top level.
Keep requesting while offset + limit < total.

Cursor lists

Two endpoint families use a cursor, and they hand the next one back in different places. GET /api/v1/webhook-endpoints/events and GET /api/v1/webhook-endpoints/{endpoint_id}/deliveries take cursor and limit, up to 200 per page. The next cursor arrives in the X-Webhook-Next-Cursor response header and is absent on the last page. Webhooks shows that loop in context. GET /api/v1/jobs takes cursor and limit, up to 50 per page. Its next cursor arrives in the response body as next_cursor, and it is null on the last page.
A cursor is opaque. Store it as an unparsed string and send it back unchanged.

Numbered lists

GET /api/v1/fonts takes page and per_page. page starts at 1, per_page defaults to 50 and accepts up to 100. The counters come back under pagination.
The last page is the one where page * per_page >= total. Fonts covers the catalogue filters.

Which endpoint uses which