PayerPrice API Documentation
PayerPrice's healthcare price transparency APIs give you access to negotiated rates, provider information, and market benchmarks across the United States. Use them to power reimbursement analytics, build provider directories, and retrieve fee schedules. ## Start here 1. [Log in](https://app.payerprice.com/app/login?utm_source=api_docs&utm_medium=referral&utm_campaign=login&redirectTo=%2Fapi%2Fdoc) or [sign up](https://app.payerprice.com/app/sign-up?utm_source=api_docs&utm_medium=referral&utm_campaign=signup&redirectTo=%2Fapi%2Fdoc) to get an API key. Then find it under [**Your API Keys**](/api/doc#description/your-api-keys). 2. Make a first request to list available payers and data periods: ```bash curl https://api.payerprice.com/api/v1/payers \ -H 'Authorization: Bearer YOUR_API_KEY' ``` 3. The response is an array of objects with a `payer` name and `yearMonths` entries. Use a returned payer and period when building a pricing request. [See the payer endpoint](/api/doc#tag/payer-apis/GET/api/v1/payers). 4. Next, [get market benchmarks](/api/doc#tag/pricing-apis/POST/api/v1/market/benchmarks) for a comparable market or [get provider rates](/api/doc#tag/pricing-apis/POST/api/v1/provider/rates) for a specific NPI, TIN, or CCN. Requests made with an API key can consume credits. Check the credit balance and [usage dashboard](https://app.payerprice.com/app/profile?tab=api-usage) before choosing **Test Request**. Test requests are sent only when you click that button. ## Integration essentials - Send `Authorization: Bearer YOUR_API_KEY` over HTTPS. A missing or invalid key returns `401`; a forbidden request returns `403`. - Invalid filters can return `400`. Insufficient API credit returns `402`. Rate limiting returns `429`; back off before retrying. Retry reads after transient failures, but do not blindly repeat create, update, or delete requests. - Pagination and asynchronous processing vary by endpoint. Follow each operation's request and response fields. Report creation can finish after the initial request; use its documented status and data-retrieval workflow. - API paths use `/api/v1`. The OpenAPI version describes this contract; payer `yearMonths` describe available source-data periods. These are separate versions. ## OpenAPI specification [Download the OpenAPI specification](/api/doc/openapi.json) using a signed-in browser session or an `Authorization: Bearer YOUR_API_KEY` header. Credentials are never embedded in the response. [Read Markdown docs](/api/doc.md) or [the API index for agents](/llms.txt).
Authentication
All requests must include an API key as a Bearer token in the Authorization header.
API Endpoints
- POST /api/v1/npis: Retrieve provider information for one or more National Provider Identifiers (NPIs).
- POST /api/v1/npiSearch: Fuzzy search for NPIs by name or NPI. Optionally filter results by taxonomy, state, county, or entity type.
- POST /api/v1/market/benchmarks: Search for **market-level aggregate statistics** and benchmarks. Results summarize published rates in the selected payer, geography, taxonomy, billing-code, and period cohort; they are not prices for
- POST /api/v1/provider/rates: Search for **published provider-specific negotiated rates** by NPI, TIN, or CCN. Preserve the matched provider identifier, payer, plan or network, billing code and type, billing class, service code, m
- POST /api/v1/ccns: Retrieve hospital information keyed by CMS Certification Number (CCN).
- POST /api/v1/ccnSearch: Search hospitals by name or CCN, with optional state, category, and facility type filters.
- POST /api/v1/tins: Retrieve provider information for one or more Taxpayer Identification Numbers (TINs). **Note:** CMS allows insurers to report provider TINs using either an NPI or Employer Identification Number (EIN).
- POST /api/v1/tinSearch: Fuzzy search for TINs by name, provider taxonomy codes, state, or TIN type (ein/npi).
- GET /api/v1/payers: Retrieve supported payers and available year/month source-data periods. A listed period means data is available for that payer; it does not establish a contract effective date for any returned rate.
- POST /api/v1/payer/plans: Retrieve the list of normalized plan names for a given payer, ordered by frequency (most common first).
For machine-readable documentation, see llms.txt or Markdown docs. OpenAPI specification available at openapi.json.