limit and the next_cursor from the previous page, and stop when next_cursor is null. Cursors stay correct while new records are created, so you never skip or repeat a record.
Last reviewed: 2026-11-04
This page covers the Partner API only; the patient REST API has its own pagination rules.
Which parameters does a list request take?
Keep the same filters on every page of one listing. For example, consultations accept
status, external_patient_id, external_reference, created_after and created_before.
What does a page look like?
results is shortened. Results are ordered newest first, by creation time. next_cursor is null on the last page.
Cursors are opaque: do not build, parse or change them. A cursor that is not valid fails with 400 invalid_cursor.
How do I read every page?
Which endpoints are paginated?
GET /v1/partner/consultations/GET /v1/partner/patients/GET /v1/partner/prescriptions/GET /v1/partner/webhook-endpoints/{id}/deliveries/
Frequently asked questions
What is the maximum page size?
- limit accepts 1 to 100 and defaults to 50; a value outside the range fails with 400 invalid_request.
In which order are results returned?
Newest first, by creation time.Can I build or decode a cursor myself?
No. Cursors are opaque: do not build, parse or change them. A cursor that is not valid fails with 400 invalid_cursor.How do I know I reached the last page?
next_cursor is null on the last page.Can I change filters between pages?
No. Keep the same filters on every page of one listing.Is the product list paginated?
No. The product list is short and returned in one response without a cursor.Next steps
Rate limits
Spread bulk reads under the limits.
Go-live checklist
The reconciliation job that uses pagination.