Skip to main content
Headout delivers webhooks over two channels:

​
Booking-status webhook

Booking-status webhooks are essential to:
  • Track ticket generation
  • Receive cancellation or reschedule updates
  • Handle failures
  • Keep booking state in sync
Partners must assume:
  • Status transitions are non-linear
  • Completed bookings can still be cancelled (ex: in case of venue closures etc)

​
Verifying authenticity

Headout does not yet sign booking-status webhook payloads. The supported workaround is IP whitelisting — accept incoming webhook traffic only from Headout’s known source IPs listed below. Signature-based verification for this channel is in progress.

​
Event subscriptions

Event subscriptions notify you of product changes without polling: register an HTTPS endpoint once and receive a signed webhook the moment a product’s listing status flips. Manage endpoints, pause and resume delivery, and rotate signing secrets entirely through the API.

​
Verifying authenticity

Every delivery is signed: the X-Headout-Signature header carries a timestamped HMAC-SHA256 over the exact request body. Verification steps and ready-made samples (Go, Java, Kotlin, Node, Python) are on the Event subscription notification page.