Sandbox & Test Environment
Build and test your Metro 2 integration with environment-aware keys and records on the same platform. Core validation behavior is shared with live processing, while test-mode records stay out of live bureau delivery.
How it works
Four steps from sandbox to production confidence.
Get test API keys
Create test-mode API keys from the dashboard. Developer accounts are limited to test keys until live access is approved.
Submit test data
Submit records through the same host and supported routes. Test-mode records are tagged and excluded from live bureau delivery.
Validate results
Review validation results, generated files, and processing status. Core validation behavior is shared with live processing.
Go live with confidence
Move to live reporting by issuing live keys on an approved account and reusing the same integration flow where supported.
Everything you need to test with confidence
Test mode gives you a safe place to validate payloads and file generation behavior without introducing live bureau-delivery risk.
Test-mode API keys
API keys can be scoped to test or live. Developer accounts can create test keys only until live access is enabled.
Environment-tagged records
All records created in the sandbox are tagged as test data. They are processed through the same pipeline but never submitted to any bureau.
Same host for test and live
Supported public routes use the same application host. Environment is carried on the key and stored on each record.
Shared validation logic
Core Metro 2 validation logic is shared with live processing so you can catch formatting and business-rule issues before go-live.
No live bureau delivery in test mode
Test-mode records are kept out of live bureau delivery flows, reducing the risk of accidental production reporting.
Straightforward go-live path
Approved accounts can issue live keys and keep the same data model and route surface for the supported public API.
Same host, environment-aware keys
Supported public endpoints use the same host for test and live traffic. Environment is carried on the key and the stored record, rather than on a separate sandbox domain. Not every live-only workflow has a separate public test equivalent.
- Same host for test-mode and live-mode submissions
- Record environment stored as test or live
- Developer accounts restricted to test keys
- Live bureau delivery excluded for test-mode records
Ready to test your integration?
Sign up and get test access. Submit records, validate files, and inspect processing behavior before switching an approved account to live reporting.