POST /api/avvo/lawyers
Price: 10 credits
Get an Avvo attorney profile by id (e.g. 1625117), profile slug or profile URL: full name, headshot, biography, Avvo Rating with label, client review star average with per-star breakdown and review count, practice areas with focus percentage and years practiced, office contact and geo, state bar licenses with status and acquired year, spoken languages, education, honors, work experience, speaking engagements, publications, sample cases, professional associations, awards, accepted payment methods, consultation offer and legal-answer / endorsement activity counts.
Fetch one Avvo attorney by id (e.g. 1625117), profile slug or profile URL. Returns id, name, alias (slug), profile_url, image, description (biography), taglines, avvo_rating (0-10) with avvo_rating_label, rating (1-5 client star average), review_count, ratings_per_star, phone, website, address/city/state/zip_code, latitude/longitude, practice_areas (name, percent, years_practiced, description), areas_served, languages, licenses (state, status, acquired_year, years_licensed, misconduct), education, honors, work_experience, speaking_engagements, publications, sample_cases, associations, awards, payment_methods, consultation, answer_count and endorsement_count.
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)@type string (default: "AvvoLawyer")id string requiredname string requiredalias string nullableprofile_url string nullableimage string nullabledescription string nullabletaglines array (default: [])avvo_rating number nullableavvo_rating_label string nullablerating number nullablereview_count integer nullableratings_per_star array (default: [])@type string (default: "AvvoRatingStar")stars integer requiredcount integer requiredpercentage number requiredphone string nullablewebsite string nullableaddress string nullablecity string nullablestate string nullablezip_code string nullablelatitude number nullablelongitude number nullablepractice_areas array (default: [])@type string (default: "AvvoLawyerPracticeArea")name string requiredpercent integer nullableyears_practiced integer nullabledescription string nullableareas_served array (default: [])languages array (default: [])licenses array (default: [])@type string (default: "AvvoLawyerLicense")state string nullablestatus string nullableacquired_year string nullableyears_licensed integer nullablemisconduct string nullableeducation array (default: [])@type string (default: "AvvoLawyerEducation")year string nullableinstitution string nullabledegree string nullablehonors array (default: [])@type string (default: "AvvoLawyerExperience")period string nullablename string nullabledetail string nullablework_experience array (default: [])@type string (default: "AvvoLawyerExperience")period string nullablename string nullabledetail string nullablespeaking_engagements array (default: [])@type string (default: "AvvoLawyerExperience")period string nullablename string nullabledetail string nullablepublications array (default: [])@type string (default: "AvvoLawyerExperience")period string nullablename string nullabledetail string nullablesample_cases array (default: [])@type string (default: "AvvoLawyerExperience")period string nullablename string nullabledetail string nullableassociations array (default: [])awards array (default: [])payment_methods array (default: [])consultation string nullableanswer_count integer nullableendorsement_count integer 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.