/ratemds/doctors

POST /api/ratemds/doctors

Price: 10 credits

Get a RateMDs doctor profile by slug (e.g. dr-angelo-ayar-tamarac-fl-us), numeric id or profile URL: full name, gender, credential, primary and secondary specialties, patient star rating with the four-criteria breakdown (staff, punctuality, helpfulness, knowledge), per-star distribution, review count, local ranking, the native-only rating, biography, a sample review, spoken languages, areas of expertise, education, accepted insurance plans, awards, publications and office locations.

How to use it

Fetch one RateMDs doctor by slug, numeric id or profile URL. Returns name, first_name/middle_name/last_name, gender, credential (e.g. MD), primary_specialty, specialty_slug, secondary_specialties, image, profile_url, verified, accepting_patients, accepting_virtual_appointments, accepting_cdcp, appointments_enabled, rating (1-5 avg over RateMDs and partner reviews), review_count, rating_organic/review_count_organic (RateMDs reviews only), the four-criteria rating_staff/rating_punctuality/rating_helpfulness/rating_knowledge, ratings_per_star, rank/rank_total, description (biography), review_snippet, languages, expertise, education, insurance, awards, publications and locations.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• doctor string required — RateMDs doctor slug (e.g. dr-angelo-ayar-tamarac-fl-us), numeric id (e.g. 41632) or a doctor profile URL (examples: "dr-angelo-ayar-tamarac-fl-us"; minLength: 1)

Response

• @type string (default: "RatemdsDoctor")
• id string required
• name string required
• first_name string nullable
• middle_name string nullable
• last_name string nullable
• gender string nullable
• credential string nullable
• primary_specialty string nullable
• specialty_slug string nullable
• secondary_specialties array (default: [])
• image string nullable
• profile_url string nullable
• verified boolean nullable
• accepting_patients boolean nullable
• accepting_virtual_appointments boolean nullable
• accepting_cdcp boolean nullable
• appointments_enabled boolean nullable
• rating number nullable
• review_count integer nullable
• rating_organic number nullable
• review_count_organic integer nullable
• rating_staff number nullable
• rating_punctuality number nullable
• rating_helpfulness number nullable
• rating_knowledge number nullable
• ratings_per_star array (default: [])
  • @type string (default: "RatemdsRatingStar")
  • stars integer required
  • count integer required
• rank integer nullable
• rank_total integer nullable
• description string nullable
• review_snippet string nullable
• languages array (default: [])
• expertise array (default: [])
• education array (default: [])
  • @type string (default: "RatemdsEducation")
  • institution string required
  • year integer nullable
• insurance array (default: [])
• awards array (default: [])
• publications array (default: [])
• locations array (default: [])
  • @type string (default: "RatemdsDoctorLocation")
  • name string nullable
  • category string nullable
  • address string nullable
  • suite string nullable
  • city string nullable
  • state string nullable
  • country string nullable
  • postal_code string nullable
  • phone string nullable
  • website string nullable
  • latitude number nullable
  • longitude number nullable
  • is_primary boolean nullable
  • profile_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Doctor not found (well-formed id with no RateMDs profile) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.