Prior Auth API
Collate turns payer-specific prior authorization work into one API workflow.
Create an Authorization, keep reading it, and take action only when the
resource asks you to.
Collate owns payer routing, portal operation, receipt capture, decision tracking, and recovery. Your integration owns clinical data, supporting documents, approval at final-submit boundaries, and human payer interaction when Collate explicitly hands it to you.
Your integration drives each case by reading the latest Authorization.
How the API works
Your system talks to the API. Collate and the payer do their work behind the durable authorization state.
status tells you who owns the next move. When status = requires_action,
nextAction.type tells you the exact customer-owned command to run. See
Authorization lifecycle for the full state machine.
What you build
Find a serviceable route
Use your provider, payer, coverage state, service type, and service code to confirm Collate can manage the payer workflow.
Create the authorization
Create one authorization for one payer submission. Send
policy.finalSubmission and a fresh Idempotency-Key.
Resolve requirements
Use the returned questionnaire contract to collect answers from your backend, an agent, imported data, or a human workflow. Patch answers and attach required documents until blockers clear.
Start here
Create and advance a sandbox authorization with copyable cURL commands.
Build route selection and create the durable case resource.
Interpret questionnaire items, patch answers, and clear document blockers.
Understand ownership, transitions, final approval, and polling.
Validate environment, access, files, approval, handoffs, and support logging.
Inspect generated endpoint schemas, request fields, and error responses.
SDKs
The REST API is the canonical integration surface. Python and TypeScript SDKs are available for organizations participating in the SDK beta.