Typical response time: under 250 ms. Covers 50 states (including OWCP).Check API status for live uptime.
What you get in every response
- Allowed reimbursement amounts per service line
- Reduction explanations and reason codes
- Step-by-step calculation logic (RuleTrace™)
- Fee schedule citations with source URLs
- A shareable QR-linked review report
How authentication works
BillSentry uses a two-header model on every request:Request and response encoding
POST /v1/facility accepts plain JSON only.
Your credentials
BillSentry will provision these during onboarding. Store them securely and treat them the same as passwords.Each API customer receives a dedicated API endpoint URL for their organization. That same URL is used for both sandbox and production. Sandbox vs production is determined by your API key (and the matching M2M credentials). Do not use another customer’s endpoint URL.You will receive separate sandbox and production credential sets (Client ID/Secret + API key). Use the matching set for each environment.
Architecture
Your dedicated API gateway:- Validates the Bearer token signature
- Confirms the token
subclaim matches your registered M2M client ID - Confirms the
x-api-keyis active, bound to your tenant, and selects sandbox or production - Proxies the request to the BillSentry processing engine (internal, you do not call this directly)