/bengo4/offices

POST /api/bengo4/offices

Price: 5 credits

Get a law office profile from Bengo4 (弁護士ドットコム): name, catch copy and description, focus and practice areas, registered lawyers with bar association, and the office overview with address, station, hours and website

How to use it

Office ids come from bengo4/offices/search. A returned lawyer id is an id for bengo4/lawyers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• office string required — Bengo4 law office id or office URL (examples: "7531", "https://www.bengo4.com/office/tokyo/a_13103/o_7531/"; minLength: 1)

Response

• @type string (default: "Bengo4Office")
• id string required
• url string required
• name string nullable
• image string nullable
• catch_copy string nullable
• description string nullable
• focus_areas array (default: [])
• practice_areas array (default: [])
• lawyer_count integer nullable
• lawyers array (default: [])
  • @type string (default: "Bengo4OfficeLawyer")
  • id string required
  • name string nullable
  • bar_association string nullable
  • image string nullable
  • focus_areas array (default: [])
• overview array (default: [])
  • @type string (default: "Bengo4LabelValue")
  • label string required
  • value string nullable

Errors

• 422 — office is not a Bengo4 law office 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 law office 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.