Environments

Collate runs two public environments with the same API contract.

Use a separate API key for each environment:

1
Authorization: Bearer <API_KEY>

Use sandbox to validate integration behavior. Use production only for live prior-authorization traffic.

Sandbox behavior

Sandbox is designed for safe integration testing. It uses the same public resources, statuses, nextAction values, errors, and concurrency model as production. Deterministic sandbox scenarios are discoverable at GET /v1/sandbox/scenarios. Each scenario returns production-shaped create data, including starter answers that select the scenario in sandbox.

Final payer submit can be disabled by non-production safety controls. When that happens, an authorization can pause at approve_submission even if the create policy was automatic. This is intentional. Your client should always follow the returned status and nextAction.

Use sandbox to prove that your integration can:

• fetch the scenario catalog and run documented deterministic lifecycle cases
• list route options and resolve exact routes
• create authorizations with policy.finalSubmission
• satisfy questionnaires from returned linkIds
• patch answers and attach files
• confirm continue_authorization and approve_submission
• poll processing and waiting_on_payer
• handle live-session and manual-handoff states without relying on internal URLs
• recover from version_conflict, review_stale, and file validation errors

Sandbox scenario selection uses normal create data, so production create bodies and lifecycle behavior remain unchanged.

Production readiness

Before switching to production, use the full Production readiness checklist.

Support

Email support@trycollate.ai for integration help and production triage. Include the environment, authorization ID, current status, current nextAction, current version, and request ID when available. Do not send unsanitized PHI or credentials.