Claims API

​

Base URL

https://api.denialbase.com

​

Before you start

• Your practice’s business associate agreement is signed. Until it is, every call answers 403 with code: baa_required.
• An owner or admin created an API key in Settings → API keys with Send claims and Read claim status. See Authentication.
• Calls come from your server. Never put the key in a web page or app.

​

Quickstart

curl -X POST https://api.denialbase.com/api/v1/claims \
  -H "Authorization: Bearer $DENIALBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "patient": { "first_name": "Jane", "last_name": "Doe", "date_of_birth": "1980-04-12",
                 "account_number": "A-1001" },
    "claim": { "claim_number": "YOUR-CLAIM-NUMBER", "payer_claim_number": "PAYER-CLAIM-NUMBER",
               "payer_name": "Blue Shield", "date_of_service": "2026-08-01", "denial_date": "2026-09-02",
               "procedure_code": "29881", "billed_amount": "1250.00", "denial_codes": ["CO-50"] }
  }'

{
  "claims": [
    { "claim_number": "YOUR-CLAIM-NUMBER", "id": "952a1c46-5a7e-48e3-9322-5bafeaf02771",
      "status": "received", "created": true }
  ],
  "submission_id": "b24894c4-a3e9-4d6e-a556-a21e86630c4b"
}

curl -G https://api.denialbase.com/api/v1/claims/status \
  -H "Authorization: Bearer $DENIALBASE_API_KEY" \
  --data-urlencode "claim_number=YOUR-CLAIM-NUMBER"

{
  "claim": {
    "claim_number": "YOUR-CLAIM-NUMBER",
    "id": "952a1c46-5a7e-48e3-9322-5bafeaf02771",
    "status": "reviewing",
    "signing": { "status": "not_decided", "appeal_button": false }
  }
}

​

Good to know

• Which number goes where. There is no claim number shared across payers. The key is the claim number your billing system already puts on the claim (the patient control number: box 26 of the CMS-1500, CLM01 in an 837), sent as claim.claim_number. The payer’s own number for the claim (ICN or DCN, from the EOB or denial letter) goes in claim.payer_claim_number: we need it to appeal, but it can change when the payer reprocesses the claim, so it isn’t the key.
• Send a claim again safely. We recognize claims by their claim number: sending one again returns the claim it became, with created: false. Retrying after a timeout, or re-sending everything each night, never creates a duplicate. A resend may correct the amounts and the payer claim number.
• One claim number, one claim. A claim number you already used for a different patient (name and date of birth), or for a different claim of the same patient (another date of service or procedure code), is refused for that claim, with an error, so a reused number never stands in for a new claim.
• A batch is all or nothing on validation. If one claim in a batch is invalid, nothing is saved and the error lists every problem. See Errors.
• We never echo patient details back. Responses carry your claim number, our id and the status.
• You don’t choose routes. Our team decides how each claim is appealed. When a patient’s signature is needed, signing tells you, and gives you the link for the appeal button while it’s switched on.

​

Claim statuses