Pagination
Read collections use keyset pagination by record ID, not page-number pagination.
Verified behavior
- Default per_page is 30
- Maximum per_page is 100
- Response meta returns has_more and next_after_id
- Send after_id=next_after_id on the next request while retaining filters
- This is not a point-in-time snapshot or updated-since feed
Response
{
"data": [ ... ],
"meta": {
"per_page": 30,
"has_more": true,
"next_after_id": 348
}
}
GET /slabs?after_id=348&per_page=30Important
All example hostnames, IDs and tokens are placeholders. Test against staging first. The installed runtime services and exact OpenAPI contract remain authoritative for state transitions, nested schemas and additional permission checks.