Sandbox Test Data
Atlas API sandbox test data for published routes, test cards, and shared validation inputs.
Use this section for published sandbox inputs used during testing.
Start here when you need to:
run stable sandbox test scenarios
find published test card data
use shared inputs for sandbox validation or UAT preparation
FAQ
What should I use Sandbox Test Data for?
Use this section for stable sandbox routes, test cards, and other published inputs used during validation.
When should I check Sandbox Test Data?
Check it before sandbox validation, scripted testing, or UAT preparation when you need known-good test inputs.
Pages in this section
What this section covers
Sandbox routes
Sandbox payment cards
Shared test inputs
Refund testing
Use these passenger last names to test refund submission outcomes:
accepted— simulates a successful refund requestrejected— simulates a failed refund request
To test workflow transitions after refund submission, contact Atlas for special sandbox configuration.
Atlas does not update your order status automatically after a successful refund request.
Maintain the order status in your system based on the refund status.
Use this when you need
Stable sandbox test scenarios
Test payment card numbers
Published test inputs for UAT or sandbox validation
What comes next?
After you pick the required test input, continue with Sandbox Development or UAT Validation.
Related sections
Last updated
Was this helpful?