Skip to main content
All endpoints require both auth headers (Authorization and x-api-key). Most accept a gzip-compressed POST body — see per-endpoint notes below for exceptions.

POST /v1/review

Primary endpoint. Submit a bill and receive a full pricing decision with RuleTrace™ calculation detail. Body: gzip JSON.

POST /v1/validate

Validate codes and determine the review jurisdiction before submitting for full review. Same request body as /v1/review. Body: gzip JSON.

POST /v1/facility

Return a list of hospitals or outpatient/surgery centers for accurate institutional pricing. Body: plain JSON (not gzip).

POST /v1/duplicates

Identify duplicate or potential duplicate service lines. Same request body as /v1/review. Body: gzip JSON.

POST /v1/customcodes

Retrieve tenant-specific procedure codes not in the standard CPT®/HCPCS list. No request body required.
All paths are appended to your API Endpoint URL — e.g. {your_api_endpoint}/v1/review.
Key naming convention: Request body fields use PascalCase (e.g. Bill, ProviderTaxID, CPT1). The API is case-insensitive for inbound requests. Response fields are returned in camelCase.

Request Body — /v1/review, /v1/validate, /v1/duplicates

The request is a JSON object. Bill, Services, Claim, and Provider are required. BillOptions and BillHistory are optional.

Bill object


BillOptions object

All fields are optional and override your tenant’s default configuration.

Services array — per service line


Claim object


Provider object


BillHistory array

Pass prior bills from the same claim to enable duplicate detection and visit-limit enforcement. Each entry has the same structure as the top-level request (a Bill object + Services array).

TypeOfBill values


ProviderType values


Request Body — /v1/facility

This endpoint accepts plain JSON — do not gzip-compress the body or set Content-Encoding: gzip.

Request Body — /v1/customcodes

No request body. Send auth headers only (Authorization and x-api-key). The response returns the list of custom codes configured for your tenant.

Response Structure — /v1/review

A successful review returns HTTP 200 with a gzip-compressed JSON body (Content-Encoding: gzip). Most HTTP clients decompress this automatically — ensure your client sends Accept-Encoding: gzip or handles decompression explicitly.

Top-level response fields


bill response fields


services[] response fields — per line


Reason Code fields


Rule Trace Entry fields

Each entry in bucketList represents one step in the pricing calculation.

Rule Trace — bucketSource values


CPT® © 2025 American Medical Association. All Rights Reserved. Fee schedules, relative value units, conversion factors and/or related components are not assigned by the AMA, are not part of CPT, and the AMA is not recommending their use. The AMA does not directly or indirectly practice medicine or dispense medical services. The AMA assumes no liability for data contained or not contained herein. CPT is a registered trademark of the American Medical Association.