Skip to the page
Chapters

Payer requests

Record a payer request

POST/api/v1/payer_requests

Records a request that came by letter or phone, about a claim (its payer) or with a payer of its own. The same payer and reference number again returns the first. Needs an Idempotency-Key header and a key with the submit permission.

Needs a key with submit permission.

Request

Headers

Headers
NameTypeRequiredDescription
Idempotency-KeystringrequiredMakes the request safe to repeat: a request with the same key and body returns the first answer (the reply has an idempotent-replayed header), and the same key with a different request is refused. 1 to 255 printable characters; a UUID is a good choice.At least 1 character.At most 255 characters.Matches `^[\x21-\x7e]{1,255}$`.

Body

Body
NameTypeRequiredDescription
claim_idstringoptionalThe claim the request is about.
payer_idstringoptionalThe payer that asks (pyr_..., a payer ID or an alias). Default: the claim's payer.
reference_numberstringrequiredThe payer's reference number, from its letter: at most 30 characters (letters, digits, spaces and ! " & ' ( ) + , - . / ; ? =).
requestedstringrequiredWhat the payer asks for, in its words.
due_datestring (date)optional

Response

The payer request. Status 201.

Response fields
NameTypeDescription
idstringAn ID that starts with prq_.
objectstringAlways `payer_request`.
statestringOne of: `open`, `answered`.
sourcestringnetwork (it arrived through the network) or staff (recorded by hand, from a letter).One of: `network`, `staff`.
claim_idstring or nullAn ID that starts with clm_.
payerobject
payer.idstringAn ID that starts with pyr_.
payer.payer_idstringThe payer's own payer ID.
payer.namestring
reference_numberstringThe payer's reference number: the answering attachment carries it.
requestedstringWhat the payer asks for, in its words.
due_datestring (date) or null
answering_attachment_idstring or nullAn ID that starts with att_.
answered_atstring (date-time) or null
created_atstring (date-time)

Errors

Errors
HTTP statusCodeWhat it means
401UNAUTHORIZEDA valid API key is required. Send it as "Authorization: Bearer <key>".
403PERMISSION_DENIEDThis API key is not allowed to do that.
422INVALID_REQUESTThe request is not valid.
400IDEMPOTENCY_KEY_REQUIREDPOST and PATCH requests need an Idempotency-Key header.
422IDEMPOTENCY_KEY_REUSEDThat Idempotency-Key was already used with a different request.
409IDEMPOTENCY_KEY_IN_USEA request with that Idempotency-Key is still running. Retry shortly.
413PAYLOAD_TOO_LARGEThe request body is larger than 1 MB.
504TIMEOUTThe request took too long to finish. It may still have taken effect: look it up before sending it again with a new Idempotency-Key. What it made is found with GET /api/v1/eligibility?request_id=<this request_id>, and the same filter on /api/v1/claims and /api/v1/attachments (a key with read permission).
503ATTACHMENTS_UNAVAILABLEAttachments are not available in live mode yet. Use a test key.
500INTERNALSomething went wrong on our side. Quote the request ID if you contact us.

Example

Example request

Shell
curl -X POST "https://sandbox.myclaimhouse.com/api/v1/payer_requests" \
  -H "Authorization: Bearer $CLAIMHOUSE_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "claim_id": "clm_01JM000000E00800000000002G",
  "reference_number": "LETTER-0915",
  "requested": "The perio chart for the scaling.",
  "due_date": "2026-10-15"
}'

Example response: 201

JSON
{
  "id": "prq_01JM000000E008000000000040",
  "object": "payer_request",
  "state": "open",
  "source": "staff",
  "claim_id": "clm_01JM000000E00800000000002G",
  "payer": {
    "id": "pyr_01JM000000E008000000000004",
    "payer_id": "00000",
    "name": "Example Dental Plan"
  },
  "reference_number": "LETTER-0915",
  "requested": "The perio chart for the scaling.",
  "due_date": "2026-10-15",
  "answering_attachment_id": null,
  "answered_at": null,
  "created_at": "2026-09-25T21:02:30.000000+00:00"
}