Skip to main content
Typical response time: under 250 ms. Covers 42+ states (including OWCP).
The BillSentry BillReview API allows technology partners and payers to submit bill data and receive structured pricing decisions that can be incorporated directly into claims or adjudication workflows.

​
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:
HeaderPurpose
Authorization: Bearer {access_token}Proves your identity (short-lived M2M JWT)
x-api-key: {api_key}Routes the request to your tenant
All request bodies must be gzip-compressed. Send Content-Type: application/json and Content-Encoding: gzip with a gzip-compressed JSON body. Uncompressed requests will be rejected.

​
Your credentials

BillSentry will provision these during onboarding. Store them securely — treat them the same as passwords.
CredentialDescriptionExample format
Client IDOAuth2 M2M client identifierm2m-client-live-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Client SecretOAuth2 M2M client secret — never expose publiclyJj8K... (64+ chars)
API KeyPer-tenant key sent in x-api-key headerbillsentry_prod_yourcompany_1234
Token URLOAuth2 token endpointProvided during onboarding
API Endpoint URLYour dedicated API gateway URLProvided during onboarding
Each API customer receives a dedicated API endpoint URL provisioned exclusively for your organization. Do not use another customer’s endpoint URL.Sandbox credentials include a separate endpoint URL and Token URL.

​
Architecture

Your System
    │
    ├─ 1. POST to Token URL ──────────────────────────────► Auth Service
    │       (client_id + client_secret)                       │
    │◄──────────────────────────────────────────────────────  │
    │       access_token (JWT, expires ~1 hour)               │
    │
    ├─ 2. POST /v1/review ───────────────────────────────► Your API Endpoint
    │       Authorization: Bearer {access_token}               │  (API Gateway)
    │       x-api-key: {api_key}                               │       │ 
    │       Content-Type: application/json                     │       │
    │       Content-Encoding: gzip                             │       ▼
    │       {gzip-compressed bill payload}                     │  BillSentry Engine
    │                                                          │  (Internal)
    │◄──────────────────────────────────────────────────────   │
    │       {review result}                                    │
Your dedicated API gateway:
  1. Validates the Bearer token signature
  2. Confirms the token sub claim matches your registered M2M client ID
  3. Confirms the x-api-key is active and bound to your tenant
  4. Proxies the request to the BillSentry processing engine (internal — you do not call this directly)