Test in the sandbox

Run the full booking flow against the sandbox without spending real funds.

Switch by host

The sandbox is a separate base URL. Point your client at it and change nothing else. The request and response bodies are identical to production.

Your credentials are bound to one environment. Keep your test build pointed at the sandbox host and your production build at the production host.

What is real

The sandbox behaves exactly like production up to the moment a booking is committed.

• Search, revalidate, rules, baggage, availability, check rate, and the activity catalogue all hit the real upstream sources. Responses match production.
• Authentication, sessions, role permissions, and session expiry all behave the same.
• The booking lifecycle, status transitions, cancellation, and refund all run against your test data.

What is simulated

Three endpoints would otherwise create a live, money-bearing booking with a supplier. In the sandbox they are simulated. No real booking is ever created. The response is shaped from real logged responses, so it looks the same.

The sandbox wallet

Your first sandbox call creates a separate sandbox office seeded with USD 10,000. Every hold, deduction, and release hits this wallet. Real funds are never touched. Read the balance with CreditBalance.