Developers
STRYK Partner API
The Partner API connects your software to one hotel in STRYK. Read room types, availability and prices, create and cancel bookings, keep guest contact data in sync, and get a signed webhook when something changes.
What you can build
- Your own booking websiteShow room types, check availability, quote a stay and create the booking directly in STRYK.
- Sync with other softwareMirror bookings, guests and invoices into a CRM, data warehouse or door-lock system, with deltas and webhooks.
- React to changesReceive
booking.updated,availability.changedand other events within seconds of the change.
The API works in both directions. Reading covers property data, availability, rates, bookings, guests, payment status and finalised invoices. Writing covers creating, changing and cancelling bookings, updating guest contact data, setting daily prices, availability restrictions and unit status, and recording bank transfers on invoices. Outgoing webhooks tell your system what changed, so you do not have to poll.
Basics
| Topic | Convention |
|---|---|
| Base URL | https://app.staystryk.com/api/partner/v1 |
| Authentication | Authorization: Bearer stryk_live_…, one key per integration and hotel, see Authentication |
| Format | JSON over HTTPS, camelCase fields, errors as RFC 9457 application/problem+json, see Errors |
| Time | Timestamps in RFC 3339 UTC (2026-11-04T08:15:00.000Z); stay dates as YYYY-MM-DD in the hotel's local time; the hotel's IANA time zone is in GET /hotel |
| Money | {"amount": "123.45", "currency": "EUR"}, a decimal string with exactly two decimal places and an ISO 4217 code |
| Lists | Cursor pagination with limit (1-200) and cursor, deltas with updated_since, see Pagination |
| Limits | 120 requests per 60 seconds per key by default, request bodies up to 64 KiB, see Rate limits |
| Versioning | Major version in the path (v1); additive changes without a new version, see Versioning |
Every response carries an X-Request-Id header and Cache-Control: no-store. Quote the request ID when you contact the hotel or STRYK support about a specific call.
Resources
The API reference lists every endpoint with parameters, schemas, examples and code. This map is generated from the same OpenAPI specification.
What the API does not do
- No card data, no payments. API v1 does not accept payments. A booking created over the API has an open balance that the hotel settles through its existing STRYK payment paths or at the front desk.
GET /bookings/{id}/paymentsshows the status. - No own price logic. Prices always come from STRYK. Your booking request can carry the price the guest saw (
expectedTotal); STRYK rejects the booking with409 conflictif the price has changed. - One hotel per key. A key belongs to exactly one hotel. Groups use one key per property.
- Server to server only. Keys must never be placed in browser or app code. Call the API from your backend.