Skip to main content

​
Sandbox environment

All products are fulfilled in sandbox. After capture, a sandbox booking moves from PENDING to COMPLETED, so you can test the full booking lifecycle with any product. The Fulfilment on Sandbox sheet lists sample products you can start with.
  • Sandbox should be used to validate: booking flow, webhooks, voucher rendering, and status transitions
Sandbox fulfilment is a dummy fulfilment and is not as exact as production. It is good enough to test the different flows of your integration, but you should still do some live testing in production before launch. See Test before launch.

​
Seatmap iframe

The Venue iframe needs no domain whitelisting in sandbox. Sandbox does not check the Referer header and allows embedding from any origin, so you can embed from localhost or any development host. Production enforces the allowlist and returns 403 for unregistered domains, so ask the Headout partnerships team to register your production domains before launch.

​
Seatmap test products

These are long-running sandbox shows, but not every date has a show. Fetch a current date and slot instead of hardcoding one: use List availabilities - Seatmap for SEATMAP products and List availabilities - Normal for SVG products. For the full list, call List products with a cityCode and filter the results client-side by inventorySelectionType (it is a response field, not a query parameter).
The sandbox environment has an expected daily downtime of up to 5 minutes between 2:00 AM and 3:00 AM IST for database maintenance. API requests during this window may fail.

​
Production environment

  • Real supplier behavior applies
  • Ticket generation follows hasInstantConfirmation
  • Cancellation and reschedule rules are enforced strictly