/ratemds/doctors/reviews

POST /api/ratemds/doctors/reviews

Price: 10 credits

Get patient reviews for a RateMDs doctor by slug, numeric id or profile URL. Covers both native RateMDs reviews (with the staff, punctuality, helpfulness and knowledge sub-ratings, helpful votes and appointment type) and partner reviews (with a review title), or restrict to one source. Each review has the overall star rating, text, reviewer name and date.

How to use it

Fetch patient reviews for a RateMDs doctor by slug, numeric id or profile URL. Optionally set source to ratemds (native) or partners. Each review has id, source, rating (1-5 stars), document_title (partner reviews), text, reviewer_name, created_at, helpful_count, the native rating_staff/rating_punctuality/rating_helpfulness/rating_knowledge sub-ratings, appointment_type and is_verified.

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 or a doctor profile URL (examples: "dr-angelo-ayar-tamarac-fl-us"; minLength: 1)
• source string nullable — Restrict to native RateMDs reviews or partner reviews; both when omitted (one of: "ratemds", "partners")
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "RatemdsReview")
• id string required
• source string required
• rating number nullable
• document_title string nullable
• text string nullable
• reviewer_name string nullable
• created_at string nullable
• helpful_count integer nullable
• rating_staff number nullable
• rating_punctuality number nullable
• rating_helpfulness number nullable
• rating_knowledge number nullable
• appointment_type string nullable
• is_verified boolean 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.