Sandbox

The sandbox airline answers like a real one, with a booking reference for every outcome, so your integration handles each of them before a real booking goes through.

Use your sandbox key (pk_test_…) and the airline code ZZ. Any surname works. Sandbox lookups finish in a few seconds, send the same webhooks as live ones, and are free: only your account's limits apply.

Booking references

Booking reference	What happens
`SBXOK1`	`completed`: one passenger, one flight
`SBXRTN`	`completed`: a return trip for two passengers
`SBXCNX`	`completed`: a journey with a connection
`SBXCAN`	`completed`, with `booking_status` `cancelled`
`SBXOTP`	`action_required` for a `one_time_code`. Send `123456` to complete it; anything else and it asks again
`SBXFNM`	`action_required` for a `first_name`. Any name completes it
`SBXMAN`	`manual_review`, then `completed` a minute later
`SBXLAT`	`completed` after 2 minutes, to try your timeouts
`SBXBAD`	`failed` with `invalid_credentials`
`SBXNFD`	`failed` with `booking_not_found`
`SBXDWN`	`failed` with `airline_unavailable`, which can be retried
`SBXCHG`	`completed`, and a monitor on it sends a change a minute after it starts

Monitoring in the sandbox

A monitor on SBXCHG sends a reservation.changed event a minute after it starts: the first flight leaves two hours later than it did. Other sandbox bookings never change, so their monitors stay quiet.