turquoise.health APIturquoise.health ↗
Search healthcare procedure prices and provider quality ratings by ZIP code. 2 endpoints cover service lookup and cost comparison across US providers.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/5475c330-c28c-4681-8bcf-1db4b28e3167/list_services' \ -H 'X-API-Key: $PARSE_API_KEY'
List all available medical service/procedure packages with their codes. Use these codes as the 'service' parameter in search_care.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer - number of available services",
"services": "array of objects, each with 'code' (string service code) and 'text' (string procedure name)"
},
"sample": {
"data": {
"total": 33,
"services": [
{
"code": "GA002",
"text": "Colonoscopy"
},
{
"code": "RA005",
"text": "MRI without Contrast"
},
{
"code": "RA000",
"text": "X-Ray"
}
]
},
"status": "success"
}
}About the turquoise.health API
The Turquoise Health API provides two endpoints for searching and comparing medical procedure costs across US healthcare providers. list_services returns a catalog of available procedure codes, while search_care accepts a service code and ZIP code to return paginated provider results with price, price relativity, distance, and care quality ratings — letting developers build cost-comparison tools without maintaining their own healthcare pricing data.
What the API Covers
The Turquoise Health API surfaces healthcare price transparency data across two endpoints. list_services returns the full catalog of searchable procedures — each entry includes a code string (used as the service parameter downstream) and a text label like "Colonoscopy" or "MRI without Contrast". This is the lookup table you call once to populate a procedure selector in your application.
Searching for Provider Prices
search_care is the core endpoint. Required inputs are service (a code from list_services, e.g. GA002) and location (a 5-digit US ZIP code). Optional parameters include distance (radius in miles), min_price and max_price (dollar filters), sort_by (price-asc or price-desc), and page for pagination. Results come back 20 per page; total_pages and total_results let you walk through the full result set.
Provider Response Fields
Each item in the providers array includes name, type (facility category), location, distance_miles, price, price_amount, price_qualifier (which clarifies the pricing basis), price_relativity (how the price compares to area averages), and care_quality rating. The combination of price and quality fields is what makes the data useful for side-by-side provider comparison rather than just raw cost lookup.
Coverage and Scope
Coverage is US-only and ZIP-code-scoped. The procedure catalog is fixed to the codes returned by list_services — not every CPT code is available, so calling list_services first to confirm coverage for your target procedures is the right approach before building dependent workflows.
- Build a procedure cost estimator that lets users enter a ZIP code and procedure type and see ranked provider prices
- Filter providers by
max_priceto surface options within a patient's estimated budget - Compare
price_relativityscores across providers to identify below-average-cost facilities in a region - Incorporate
care_qualityratings alongside price data to weight provider recommendations - Paginate through
search_careresults to aggregate full regional pricing datasets for a given procedure code - Populate a procedure selector UI using
list_servicescodes and human-readabletextlabels - Analyze price variance by running
search_carewithsort_by=price-descvsprice-ascacross multiple ZIP codes
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Turquoise Health offer an official developer API?+
What does `price_qualifier` mean in the `search_care` response?+
price_qualifier clarifies the basis of the reported price — for example, whether it reflects a negotiated rate, a cash price, or a chargemaster rate. It is important to read this field alongside price_amount because the same dollar figure can mean different things depending on the qualifier.Does the API support searching by provider name or filtering by provider type?+
search_care filters by service code, ZIP code, distance, and price range. Provider name and type are available in the response for each result, but they cannot be used as input filters. You can fork this API on Parse and revise it to add a provider-name or facility-type filter endpoint.How does pagination work in `search_care`?+
total_results, total_pages, and results_on_page so you can determine how many pages exist and iterate through them using the page parameter.Does the API cover procedures outside the `list_services` catalog, such as arbitrary CPT codes?+
list_services are searchable via search_care. If a CPT code you need is not in that catalog, results will not be available for it. You can fork this API on Parse and revise it to extend coverage to additional procedure codes or code systems.