Skip to main content

​
Required inputs

You must provide either:
  • lat and lng, or
  • location (ZIP or City[, State]).
If neither can be resolved, the API returns 422. Location strings resolve to the centroid of matching provider locations. For tight radii, prefer explicit lat/lng.

​
Query patterns that work well

curl "http://localhost:7860/v1/providers/search?lat=37.7749&lng=-122.4194&radius_miles=5&limit=5"

​
Geo + specialty + insurance + telehealth

curl "http://localhost:7860/v1/providers/search?location=San%20Francisco,CA&radius_miles=25&specialties=Anxiety&insurance=Aetna&telehealth_only=true&limit=10"

​
Multiple specialties

Repeat the query param: 
curl "http://localhost:7860/v1/providers/search?location=94103&specialties=Anxiety&specialties=Depression"

​
Ranking and filtering behavior

Results are filtered, then ranked:
  1. Active providers inside the radius.
  2. Optional filters: accepting_new_patients, telehealth_only, specialties, insurance.
  3. Rank order:
    • accepting new patients first
    • insurance match boost (when provided)
    • nearest distance
    • most recently verified

​
Response fields to rely on

  • distance_miles is computed from the matched location to your search center.
  • location is a single formatted string built from address fields.
  • credentials is split into a list when the source string uses commas.
  • offers_telehealth and accepting_new_patients may be null if unknown.
For exact schemas, use the API reference pages backed by the live OpenAPI spec.