POST /api/avvo/lawyers/reviews
Price: 10 credits
Get client reviews for an Avvo attorney by id, profile slug or profile URL: reviewer name, star rating, review title, review text, date and whether the reviewer hired the attorney. Optionally narrow to a star rating or to reviews mentioning a specific aspect (theme).
Fetch client reviews for an Avvo attorney by id, profile slug or profile URL. Each review has id, author, rating (1-5 stars), review_title, text, created_at and is_hired. Optional filters: rating (1-5) and theme (review aspect, e.g. Case Results, Communication Style).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)lawyer string required — Avvo attorney id (e.g. 1625117), profile slug or profile URL (examples: "1625117"; minLength: 1)count integer required — Max number of reviews to return (min: 1)rating integer nullable — Only reviews with this star rating (1-5) (min: 1; max: 5)theme string nullable — Only reviews mentioning this aspect (e.g. Case Results, Communication Style) (one of: "Case Results", "Advocacy", "Practice Area Knowledge", "Recommendation", "Professionalism", "Communication Style", "Compassion", "Responsiveness", "General Knowledge", "Character & Conduct", "Cost of Services", "Trustworthiness", "Staff & Support", "Free Consultations", "Payment Plans", "Punctuality")@type string (default: "AvvoLawyerReview")id string requiredauthor string nullablerating integer nullablereview_title string nullabletext string nullablecreated_at string nullableis_hired boolean nullable422 — 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 — Attorney not found (well-formed id with no Avvo 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.