Concepts
Pagination and deltas
All lists use cursor pagination. A cursor stays valid while data changes, so you neither skip nor repeat items in a run.
Parameters and response
| Parameter | Meaning |
|---|---|
limit | Items per page, 1 to 200, default 50 |
cursor | The nextCursor of the previous page. Keep all other parameters unchanged. |
updated_since | RFC 3339 timestamp; returns items with updatedAt greater than or equal to it |
curl "https://app.staystryk.com/api/partner/v1/bookings?limit=50&arrivalFrom=2026-12-01" \
-H "Authorization: Bearer $STRYK_API_KEY"{
"data": [
{ "id": "9d3c1b2a-…", "reference": "B-2026-01482", "updatedAt": "2026-11-04T08:15:00.000Z", "…": "…" }
],
"nextCursor": "eyJ1IjoiMjAyNi0xMS0wNFQwODoxNTowMC4wMDBaIiwiaSI6IjlkM2MxYjJhIn0",
"hasMore": true
}curl "https://app.staystryk.com/api/partner/v1/bookings?limit=50&arrivalFrom=2026-12-01&cursor=eyJ1IjoiMjAyNi0xMS0wNFQwODoxNTowMC4wMDBaIiwiaSI6IjlkM2MxYjJhIn0" \
-H "Authorization: Bearer $STRYK_API_KEY"Stop when hasMore is false; nextCursor is then null. Treat cursors as opaque strings: do not decode, build or store them for longer than a run.
Ordering
Lists are sorted by updatedAt ascending, then by id. An item that changes during your run moves to the end and appears again later, compare updatedAt and keep the newer copy.
Incremental reads
updated_since is inclusive. Pass the newest updatedAt from your last run; items with exactly that timestamp arrive again. Deduplicate by id + updatedAt. A complete example is in the sync guide.