Create a managed prior authorization
Queues a managed prior-authorization request for review and payer-portal submission. A 202 response means the request was received; it does not mean it was submitted to the payer.
Authentication
Request
A CalAIM Community Supports referral. It names a member and a service and carries no diagnosis codes, procedure codes, place of service, service facility, rendering provider, or plan of care: the payer’s Community Supports intake has no such fields, and the DHCS ECM and Community Supports HCPCS codes belong on the resulting claim rather than on this request.
An outpatient therapy authorization request. The API still accepts a body with service_type omitted and treats it as PHYSICAL_THERAPY, for compatibility with integrations that predate Community Supports; new integrations should always send it.
An outpatient therapy authorization request. The API still accepts a body with service_type omitted and treats it as PHYSICAL_THERAPY, for compatibility with integrations that predate Community Supports; new integrations should always send it.
An outpatient therapy authorization request. The API still accepts a body with service_type omitted and treats it as PHYSICAL_THERAPY, for compatibility with integrations that predate Community Supports; new integrations should always send it.
An outpatient therapy authorization request. The API still accepts a body with service_type omitted and treats it as PHYSICAL_THERAPY, for compatibility with integrations that predate Community Supports; new integrations should always send it.
Response
Partner-generated idempotency key. Replays with an identical body return the existing request; a different body returns 409.
Two-digit CMS place-of-service code for the requested care.
REAUTHORIZATION also requires previous_authorization. INITIAL is used for a new patient, condition, or payer-defined new episode.
Requested CPT/HCPCS codes. Procedure-level units and dates are optional when the plan_of_care supplies the visit-level request.
Existing uploaded document IDs with semantic types. Upload the file first: POST /images/v1 returns an id, a version and a signed_url; PUT the bytes to that signed_url; then PUT /images/v1/{id}/{version} with status UPLOADED, where the version segment is the current version plus 1 (so 1 for a freshly created image). Use the image id as document_id. Documents are optional at intake; missing payer-required documents produce NEEDS_INFORMATION.
URGENT requires urgency_reason and should only be used when the payer’s expedited-review standard is met.
Escape hatch for payer questions discovered during requirements review. Use stable snake_case keys supplied by Taiga.