/avvo/questions

POST /api/avvo/questions

Price: 5 credits

Get an Avvo legal question by id (e.g. 6315997), slug or URL: question title and body, legal topic, asker location, date and answer count, plus every attorney answer with the answering lawyer's name, specialty, star rating, review count and Avvo Rating, the answer text, date and helpful / lawyer-agree counts.

How to use it

Fetch one Avvo legal question by id (e.g. 6315997), slug or URL. Returns id, question_title, text (body), topic, topic_slug, asker_location, created_at, answer_count, url and answers (each with id, text, created_at, helpful_count, agree_count and lawyer: id, name, profile_url, specialty, rating, review_count, avvo_rating).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — Avvo legal question id (e.g. 6315997), question slug or question URL (examples: "6315997"; minLength: 1)

Response

• @type string (default: "AvvoQuestion")
• id string required
• question_title string required
• text string nullable
• topic string nullable
• topic_slug string nullable
• asker_location string nullable
• created_at string nullable
• answer_count integer nullable
• url string nullable
• answers array (default: [])
  • @type string (default: "AvvoQuestionAnswer")
  • id string required
  • text string nullable
  • created_at string nullable
  • helpful_count integer nullable
  • agree_count integer nullable
  • lawyer object nullable
    • @type string (default: "AvvoAnswerLawyer")
    • id string nullable
    • name string nullable
    • profile_url string nullable
    • specialty string nullable
    • rating number nullable
    • review_count integer nullable
    • avvo_rating number 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 — Question not found (well-formed id with no Avvo question) 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.