/bengo4/questions

POST /api/bengo4/questions

Price: 10 credits

Get a legal question from the Bengo4 (弁護士ドットコム) public Q&A board: title, categories, full question text, publication and consultation dates, and every lawyer answer with the answering lawyer, ranking, areas, posting time and best-answer mark

How to use it

Question ids come from bengo4/questions/search or bengo4/lawyers/questions. The asker is anonymous on Bengo4, so the record carries no asker identity; answering lawyer ids work with bengo4/lawyers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — Bengo4 question id or question URL (examples: "1510389", "https://bbs.bengo4.com/questions/1510389/"; minLength: 1)

Response

• @type string (default: "Bengo4Question")
• id string required
• url string required
• categories array (default: [])
  • @type string (default: "Bengo4Category")
  • id string required
  • name string nullable
• text string nullable
• published_at integer nullable
• consulted_date integer nullable
• lawyer_count integer nullable
• answer_count integer nullable
• has_best_answer boolean nullable
• answers array (default: [])
  • @type string (default: "Bengo4Answer")
  • lawyer_id string nullable
  • lawyer_name string nullable
  • lawyer_url string nullable
  • lawyer_image string nullable
  • lawyer_ranking string nullable
  • lawyer_areas array (default: [])
  • text string nullable
  • created_at integer nullable
  • is_best_answer boolean nullable

Errors

• 422 — question is not a Bengo4 question id or URL 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 — No Bengo4 question under that id 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.