Skip to main content
POST
Create Payor Inference
We support two different strategies for payor inference: NEAR_REALTIME and BASE. We recommend using NEAR_REALTIME when you want to get a response quickly (in a matter of seconds) and BASE when you want to get a more accurate response (in a matter of minutes). Currently, we only support NEAR_REALTIME and submitting with BASE will run with the NEAR_RELATIME strategy. As this is an async endpoint, you will have to make a POST request to this endpoint and then poll the response using the GET Payor Inference endpoint until status=COMPLETED or status=FAILED.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
strategy
enum<string>
required
Available options:
NEAR_REALTIME,
BASE
provider_id
string<uuid>
required

Required provider identifier (for HIPAA compliance)

patient_document_file_ids
string<uuid>[] | null

Optional list of document file IDs to process

Required array length: 1 - 10 elements
text
string | null

Payor Text

Required string length: 1 - 5000
patient_id
string<uuid> | null

Optional patient identifier

Response

id
string<uuid>
required