Skip to main content
Some payers ask for more information than the schema requires of every request. When this capability is enabled for your account, a request for one of those payers must include the payer’s additional inputs on top of the schema’s required fields.
This is an opt-in capability — ask your account team to enable it. When it’s off, a request’s required inputs are exactly the fields returned by GET /v1/schemas/{schemaId}/required-inputs.

​
What changes

Which inputs are required can depend on the payer you name in inputs.payerName. A field that’s optional for one payer may be required for another, so the schema’s required-input list is the baseline — not always the complete list for a specific payer.

​
How to handle it

If a request is missing an input a payer requires, POST /v1/requests returns INVALID_INPUTS with the field listed in details.missingInputs — the same response as any other missing required input: 
{
  "error": "INVALID_INPUTS",
  "message": "Required inputs are missing or invalid.",
  "details": {
    "missingInputs": ["claimNumber"]
  }
}
  • Add whatever appears in details.missingInputs and retry. That list tells you exactly what the request still needs.
  • Send every input you have. Populating the optional fields from the schema lookup, not just the required ones, avoids most payer-specific rejections.
  • Ask your account team which payers have additional requirements if you’d like to supply them up front.