Skip to main content
Rather than waiting for the next scheduled nightly sync, your platform can push updates to Seyaha the moment your catalog or availability changes. Seyaha exposes two inbound webhook endpoints for this purpose. Both endpoints authenticate via the x-webhook-secret header — the secret is generated when you register your integration.

Trigger a catalog sync

Call this when products are added, removed, or have pricing/metadata changes:
Seyaha will call your GET /products endpoint immediately and process any changes. Response:
skipped: true means the response hash matched the previous sync — no changes written.

Push an availability change

Call this when a single slot’s status, capacity, or vacancies change. This is faster than a full sync and avoids re-fetching the entire catalog.
Response:
If updated is false, Seyaha could not match the productId/optionId to an existing activity in its database and will trigger a full background sync automatically.

Choosing sync vs. notify

Your webhook_secret is shown once at registration. Store it in a secrets manager. If lost, you need to delete and recreate the integration to get a new secret.