/justia/lawyers

POST /api/justia/lawyers

Price: 5 credits

Get a Justia attorney profile by id (e.g. 71886), profile slug or profile URL: full name, headshot, job title, law firm, biography, years of experience, practice areas, jurisdictions, Justia Lawyer Rating with per-competency breakdown and review count, office contact and geo, education, bar and professional associations, linked social and external directory profiles, and consultation flags.

How to use it

Fetch one Justia attorney by id (e.g. 71886), profile slug or profile URL. Returns id, name, alias (slug), profile_url, image, job_title, firm, description (biography), years_experience, practice_areas, jurisdictions, languages, justia_rating (0-10) with justia_rating_best and rating_components, review_count, phone (primary) with phones (all office numbers), fax, office_hours, website, address/city/state/zip_code, latitude/longitude, education, associations, social_links, is_free_consultation, offers_video_conferencing and is_claimed.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lawyer string required — Justia attorney id (e.g. 71886), profile slug or profile URL (examples: "71886"; minLength: 1)

Response

• @type string (default: "JustiaLawyer")
• id string required
• name string required
• alias string nullable
• profile_url string nullable
• image string nullable
• job_title string nullable
• firm string nullable
• description string nullable
• years_experience integer nullable
• practice_areas array (default: [])
• jurisdictions array (default: [])
• languages array (default: [])
• justia_rating number nullable
• justia_rating_best number nullable
• review_count integer nullable
• rating_components array (default: [])
  • @type string (default: "JustiaLawyerRatingComponent")
  • name string required
  • score number required
• phone string nullable
• phones array (default: [])
• fax string nullable
• office_hours array (default: [])
  • @type string (default: "JustiaOfficeHours")
  • days array (default: [])
  • opens string nullable
  • closes string nullable
• website string nullable
• address string nullable
• city string nullable
• state string nullable
• zip_code string nullable
• latitude number nullable
• longitude number nullable
• education array (default: [])
• associations array (default: [])
• social_links array (default: [])
• is_free_consultation boolean nullable
• offers_video_conferencing boolean nullable
• is_claimed 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 — Attorney not found (well-formed id with no Justia 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.