Partner API: manage keys and webhooks
With the Partner API, you connect your own booking pages, apps and integrations with STRYK. You create keys with exactly the permissions needed and set up webhooks.
Contents
Before you start
- You need the permission Manage channels. Only then do you see the API row on the Channels page.
- Clarify which areas the integration must read or write. A key only gets these permissions.
- An integration calls the Partner API from its server. Never put the key in browser code or in an app. You find endpoints, parameters and examples in the Developer documentation. There, the section Authentication and scopes explains what each permission allows.
- Webhooks need a recipient with an address that starts with https://.
Open the API
In STRYKChannels
- Under Own connections, select the API row with the addition “API keys and webhooks”. The API dialog opens.
- Select the tab API keys or Webhooks. With Developer documentation in the dialog header, you open the developer portal.
- Tabs API keys and Webhooks
- Key with permissions
- Key actions
Create API key
In STRYKChannelsAPIAPI keys
- Select Create API key. The dialog Create API key opens.
- Enter the Name, for example “Booking page”.
- Under Permissions, choose a pattern: Read only (read all areas), Read & write (write where possible) or Custom. With Custom, you choose for each area No access, Read or Write. The areas are Hotel & rooms, Availability, Rates & plans, Bookings, Guests, Payments and Invoices. Write includes Read. Invoices are the fiscal documents of the hotel and can only be read via the API.
- Optional: Open Advanced. Choose the Expiry: No expiry, 30 days, 90 days, 1 year or Date (from tomorrow, at most three years ahead). Under IP restriction, enter one address or CIDR network per line, at most 20. An empty field allows all addresses. Under Note, you record an internal note.
- Select Create. STRYK shows API key created with the key and the note Visible only now.
- Copy the key and store it, for example in your password manager. Select Done.
Manage keys
In STRYKChannelsAPIAPI keys
The list shows for each key the Name, the start of the key, the Permissions, Created, Last used, Expiry and the status: Active, Expires soon, Revoked or Expired. Select a key to see its Permissions, Expiry, Allowed IP addresses, Rate limit (requests per minute), Usage, Recent requests and the History.
- In the row, open the menu Options.
- Select Roll if the integration should get a new key with the same permissions. Under Current key, select Old key stays valid for 24 h so you can switch the integration over, or Revoke immediately. Confirm with Roll. STRYK shows the new key once.
- Select Revoke and confirm Revoke API key? to block a key immediately. STRYK then rejects requests with this key.
Set up webhooks
In STRYKChannelsAPIWebhooks
A webhook sends the selected events over HTTPS to your systems, signed.
- Select Create webhook. The dialog New webhook opens.
- Enter the Endpoint URL, for example https://crm.nordlicht.invalid/hooks/stryk. The address must start with https://.
- Optional: Enter a Description, for example “Bookings to our CRM”.
- Under Events, select at least one: Booking created, Booking updated, Booking cancelled, Guest changed, Availability changed, Price changed, Payment changed or Unit status changed. Use Select all and Clear selection to choose all or none.
- Select Create webhook. STRYK shows Your signing secret once.
- Store the secret in your receiver. The developer documentation describes how the receiver checks the signature under Webhooks and signature verification.
- Select the webhook and then Send test event. STRYK reports “Test event is being delivered.”
Manage webhooks
Ort: Channels > API > Webhooks, select the webhook
- Use the switch Delivery active to pause or activate the webhook. Paused webhooks receive no events. After activation, delivery starts with new events.
- Last 7 days, Last success and Last failure show the status. Under Deliveries, you see each delivery with its HTTP status and Attempts. Use Send again to repeat a delivery.
- Rotate secret generates a new secret. The previous secret remains valid for 24 hours so you can switch the receiver.
- Use Edit to change the address and events, and Delete with the confirmation Delete webhook? to remove it. The delivery log is kept for 30 days.
Check the result
- For the key, Last used shows the date as soon as the integration uses it. Requests 24 h counts the requests.
- For the webhook, Last 7 days shows “{Zahl} delivered, {Zahl} failed”, and the test event appears under Deliveries.
If something does not work
| What you see | Cause | How to fix it |
|---|---|---|
| “Choose at least one permission.” | No area has a permission. | Choose a pattern or give at least one area Read or Write. |
| “Please enter a name.” | The Name is missing. | Enter a name. |
| “Please check:” followed by an address | An address under IP restriction is invalid. | Correct the address or the CIDR network. At most 20 entries are allowed. |
| “Please choose a date from tomorrow, at most three years ahead.” | The expiry date is outside the allowed range. | Choose a date from tomorrow that is at most three years away. |
| “The address must start with https://.” | The Endpoint URL is not an HTTPS address. | Enter an address that starts with https://. |
| “Choose at least one event.” | The webhook has no event. | Under Events, choose at least one. |
| Paused after repeated failures | The receiver does not respond with a 2xx status. | Check whether the receiver is reachable and select Reactivate. |
| “Activate the webhook to send a test event.” | The webhook is paused. | Activate Delivery active and send the test event. |
| “The selection could not be loaded. Please close it and open it again.” | The list of permissions and events did not load. | Close the dialog and open it again. |