Daybook API
Plug Daybook into the way you already work.
Daybook calls payers, works their portals, runs clearinghouse transactions and reads every remit and denial. You ask over the API, we tell you over webhooks, and your team stays in the systems it uses today.
POST
/v1/callsRequest- payer
- bayline
- call_type
- claim_status
- claim
- clm_8Hq2Lm
- metadata
- ticket: TCK-55821
Minutes later, on your webhook
call.completedWebhook- status
- denied
- reason
- CO-197 auth missing
- reference
- BHP-4471-0092
- next_step
- submit retro auth
POST
/v1/eligibility/checksRequest- payer
- bayline
- member_id
- W000000001
- service
- 30
- provider
- npi 1999999984
A re-check finds the plan ended
coverage.changedWebhook- check
- elig_01JBXQ0
- previous
- active, Choice PPO
- current
- inactive
- ends
- 2026-10-15
POST
/v1/claim-status/checksRequest- payer
- keystone
- claim
- A-20817-1
- date
- 2026-09-30
- billed
- $410.00
When the 277 says something new
claim.status_changedWebhook- previous
- in_process
- current
- paid
- paid
- $312.00
- check
- cs_01JBXE4H9M2T
POST
/v1/appealsRequest- denial
- den_01JBXG2N5R8W
- signer
- Alex Biller
- title
- Billing Manager
- documents
- auth_approval.pdf
When the letter is ready to review
appeal.draftedWebhook- appeal
- apl_01JBXH6Q0T3Y
- status
- ready
- letter
- pdf_url, text
- denial
- den_01JBXG2N5R8W
APIs by workflow
Find the APIs and events you need by the work your team does every day: reaching payers, getting set up, and following a claim until it is paid.
Payer callsCall the payer, work the phone tree, wait on hold, and get a structured answer back.
- Check a claim by phone
- Recheck until it moves
- Hand a live rep to a biller
- Trace a payment
- Find a missing remit
- Check an appeal
- Send an attachment
- Catch an overpayment
- Onboard a new provider
- Clear the paperwork
- Switch a bank account
- Audit coverage
- Verify before the visit
- Estimate what the patient owes
- Catch terminated coverage
- Escalate to a call
- Chase silent claims
- Confirm a payment
- Catch denials early
- Escalate to a call
- Post a payment
- Reconcile the bank
- Find missing remits
- Route denials
- Work denials by cause
- Appeal missing auth
- Resubmit coding errors
- Watch the deadline
Use cases
What teams build on Daybook, each with a prompt you paste into Claude, ChatGPT or Cursor to build it. See every use case.
Billing companiesNightly claim status sweep into your PM systemEvery unpaid claim checked over 276/277 overnight, and only the claims that moved come back to you.PracticesVerify coverage before every visitTomorrow's schedule checked over 270/271 tonight, with inactive coverage flagged before the patient arrives.RCM and EHR vendors835 to posting in your PM systemEvery 835 matched to its claims and deposit, and posted to the PM system once a person approves it.Billing companiesA Claude agent that works your AR listClaude checks each claim, reads the payer's last answer and the denial, and drafts the appeal for a person to approve.
Three ways in
APIsYou ask. Start a call, a portal task, an eligibility check or an appeal draft with one request.WebhooksWe tell you. Signed events land in your system the moment a payer answers, a remit arrives or a denial is sorted.MCPYour agents ask. The same operations as tools for Claude, Cursor or any MCP client.
Running on your data
Daybook takes your existing worklists and exports as input, so you don't rebuild your data collection. Your rules, call scripts and training docs become the instructions Daybook follows, so it does what you'd tell a biller and moves on to the next account. Results come back over the API, as webhooks, or as a file.