Skip to content
Partner API with developer portal

Your systems read from and write to STRYK directly.

Your own booking site, a revenue tool or your agency’s housekeeping app: the Partner API connects them to your hotel’s bookings, rates, availability and room status. You decide what each API key is allowed to do. We publish the reference, guides and code samples openly in the developer portal, so your developers can get started without a detour.

Partner API reference, permissions and webhooks: Open the developer portal

Read and write

Bookings, daily rates, availability, cleaning status and bank transfers.

Signed webhooks

STRYK reports changes to bookings, guests, rates, payments and rooms.

Keys with scopes

Each key belongs to one hotel, with permissions, expiry and an IP allowlist.

Open documentation

Quickstart, guides and OpenAPI reference in English and German.

Read and book

A booking site that calculates with your hotel’s real rates.

The Partner API provides the hotel, room types, units, availability and daily rates. For each request STRYK calculates a quote using the same rules as the booking engine, including tourist tax and mandatory extras. You create the booking with an idempotency key, and if you want, STRYK sends the guest its usual confirmation email.

  • Quotes with server-side pricing
  • Create, update and cancel bookings
  • Read guests, payment status and issued invoices
  • Cancellation under the hotel’s own policy
Rates and availability

Your revenue tool sets daily rates straight in the rate calendar.

With rates:write a tool writes daily rates per room type, for up to 366 days per call. The minimum and maximum prices of your room types still apply, and an empty price resets the day to your pricing rules. With availability:write it creates closures, allotment caps and arrival or departure restrictions, and can only delete the ones it created.

  • rates:write for daily rates per room type
  • availability:write for restrictions and caps
  • Room type limits stay in force
  • Every rate change logged with the key reference
STRYK pricing: reception creates a price rule that raises the Panorama Studio by 10 % on Fridays and Saturdays. After saving, the price calendar shows the new weekend prices straight away.
Rooms and payments

Room status from the housekeeping app, bank transfers from accounting.

With property:write an app sets a unit’s cleaning status, for example from dirty to inspected. If-Match protects against outdated versions, while occupancy, blocks and master data stay in STRYK. With payments:write a system records a received bank transfer against an issued invoice, up to the open amount.

  • Cleaning status with version check
  • Bank transfer against an issued invoice
  • Invoices remain receipts in STRYK
  • Repeated calls covered by idempotency
STRYK Housekeeping: Ewa Nowak opens room 105, starts the cleaning, ticks off the four checklist items and finishes. The room is done and ready for the arriving guest.STRYK Housekeeping: Eine Reinigungskraft öffnet Zimmer 105, hakt die Aufgaben ab und schließt das Zimmer ab. Es steht fertig für die Anreise bereit.
Keys and webhooks

You decide who gets access. STRYK tells you what changes.

An admin creates an API key under Channels → API, with scopes per area, an expiry date and, if needed, an IP allowlist. When you rotate it, the old key stays valid for another 24 hours or stops at once. STRYK signs webhooks such as booking.created, rate.changed or unit.updated with HMAC-SHA256, retries them on failure and lists them in the delivery log.

  • Write access includes read access
  • 120 requests per minute by default
  • Delivery log with “Resend”
  • Keys can be revoked at any time
Facility technology

Door lock, telephone, TV and Wi-Fi work with STRYK.

Alongside the partner API, STRYK connects the technology of your property. Check-in, room changes and check-out act on keys, telephone system, hotel TV and Wi-Fi access, without the front desk typing anything twice.

From idea to a running integration.

How you and your developers work through it together.

  1. 01

    Create a key

    The admin picks only the scopes the integration needs. STRYK shows the key once.

  2. 02

    Build against the reference

    Your developers start with the quickstart and code samples in JavaScript or Python.

  3. 03

    Start with read access

    Read first, then test write calls with test data agreed with the hotel.

  4. 04

    Connect webhooks

    Signed events keep the connected system in step with STRYK.

Who works with it.

Developers and agencies

Build booking sites, sync services and tools against a documented OpenAPI reference.

Managers and admins

Issue keys with exactly the permissions needed and revoke them when a partnership ends.

Revenue and housekeeping

Keep working in their usual tool while rates and room status arrive directly in STRYK.

Common questions: API & integrations

Where do I find the technical documentation?

In the STRYK developer portal at /developers: getting started, authentication, permissions, endpoints, webhooks, errors and rate limiting. The OpenAPI reference of the POS interface is available there as YAML and JSON.

What can the Partner API do?

Read property, categories, units, rates, availability and daily prices, calculate quotes, read, create and cancel bookings and change contact details and notes. It also reads guests and changes their contact details, and reads payment status and issued invoices. With write permissions it also sets the cleaning status of units, availability restrictions and daily prices, and records incoming bank transfers against invoices.

How do I get a key?

An admin of the hotel creates it in STRYK under Channels → API and chooses the permissions, for example read-only access to availability and rates. Every key belongs to exactly one hotel.

What does using the interfaces cost?

The documentation is free for developers. The hotel uses the Partner API without an add-on, within the STRYK base price of. Connecting tills is part of the STRYK POS add-on.

Which webhooks are there?

booking.created, booking.updated, booking.cancelled, guest.updated, availability.changed, rate.changed, payment.updated, unit.updated and webhook.test. Every delivery is signed with HMAC and retried automatically on errors.

How is access secured?

Every key belongs to exactly one hotel and has its own permissions, an expiry date and, if required, an IP allowlist. Webhooks are signed with HMAC, requests are rate-limited, and the hotel can revoke a key at any time.

Show more questions
Can I take payments through the API?

No. Card data and online payments do not run through the API. New bookings start with an open balance, which the hotel collects through its payment methods. You read the payment status through the API, and with write permission it records incoming bank transfers against an invoice.

Is STRYK certified for particular tills?

No. We do not call any till “certified” or any brand “supported” until a completed connection is proven. Ask us about the status for your system.

Show us what you want to connect.

Try STRYK for 14 days with your property, or talk to us about your integration in a demo. The reference is always available in the developer portal.

Questions about STRYK?