Production readiness

Separate environments

Use separate API keys for sandbox and production. Make the base URL an environment-specific setting, not a hard-coded value.

Verify provider setup

Confirm that every production providerNpi is visible to your organization and can resolve the payer routes you plan to send.

Use Choose a route and create for route validation.

Validate route coverage

For each payer, coverage state, request type, and service-code family you plan to send, verify that route resolution succeeds in the target environment.

Map questionnaires from returned linkIds

Treat the current questionnaire returned by the authorization as the answer contract. Store source-system mappings by route context when items vary by payer or service.

Exercise files and final approval

Upload, complete, and attach real document types in sandbox. Confirm that your approval workflow handles approve_submission and stale snapshots.

Prepare operations

Log the environment, authorization ID, current status, current nextAction, current version, request ID, and sanitized payload details for support and replay.