PAS Submit

post

https://example.com/priorauth/v1/fhir/2.1/pas/submit

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Submits a Claim bundle to the configured PAS provider for prior authorization. This endpoint does not currently enforce its own authentication — an Authorization header, if supplied, is simply forwarded upstream.

❗️
CAUTION
Please do not submit PHI or PII data in the TryIt! interface (sandbox environment).

❗️
IMPORTANT
Please note that unlike the previous X12 example, the JSON request requires you to provide all the required field values. Please note that these required values are GREYED out, which are pre-populated example values and can be selected to view their respective canned response. To view the required fields, expand the + symbol highlighted in dark blue in the following figure (also shown in the preceding request example). For more information, please refer to the JSON-to-EDI Content section.

Body Params

A FHIR Bundle (type collection) containing the Claim resource (and any supporting Patient/Coverage/Organization/Practitioner/DocumentReference resources) to submit for prior authorization. Inline attachments included in DocumentReference/Binary entries are extracted and stored separately before the bundle is forwarded to the PAS provider.

Prior Authorization Service submit request body. Note: the FHIR Bundle is wrapped inside a bundle property alongside pas_version, rather than being the top-level request body itself.

bundle

object

required

FHIR Bundle containing the Claim.

pas_version

string

Defaults to 2.1

PAS IG version (default: 2.1)

Headers

Authorization

string | null

Optional bearer/OAuth header forwarded as-is to the PAS provider. Not validated or enforced by this API itself.

x-chng-trace-id

string | null

Optional client-supplied correlation identifier, preferred over x-optum-trace-id when both are present.

x-optum-trace-id

string | null

Optional client-supplied correlation identifier used to trace the request across systems. The resolved trace id (inbound or generated) is echoed back on this same header in the response.

Responses

`bundle`).

Language

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

PAS Submit

❗️
CAUTION

❗️
IMPORTANT

`bundle`).

❗️CAUTION

❗️IMPORTANT

200The PAS provider processed the submission. The response body is passed back exactly as received from the PAS provider — typically a FHIR Bundle containing a ClaimResponse.

400Rejected before any call to the PAS provider, either because malware scanning flagged an inline attachment or the attachment failed local validation (e.g. an empty or oversized decoded payload). Only applies to submit, since this route (unlike inquire) externalizes attachments first.

422The request body is syntactically valid JSON but fails schema validation (e.g. missing bundle).

502Returned when an attachment could not be stored, or when the call to the PAS provider failed, timed out, or returned a response that could not be processed.

defaultAny other status code the PAS provider returns (400, 404, 500, etc. with a JSON body) is passed through verbatim — this route does not remap or wrap the provider's status code or body.

❗️
CAUTION

❗️
IMPORTANT

`bundle`).