/bengo4/lawyers

POST /api/bengo4/lawyers

Price: 20 credits

Get a lawyer profile from Bengo4 (弁護士ドットコム): name and reading, office, address, coordinates, phone, enquiry hours, practice areas with handled matters, introduction, bar association and registration year, career and education, office details and fee tables

How to use it

Lawyer ids come from bengo4/lawyers/search or the answers in bengo4/questions. Case studies are bengo4/lawyers/cases and answered questions bengo4/lawyers/questions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lawyer string required — Bengo4 lawyer id or profile URL (examples: "118581", "https://www.bengo4.com/kyoto/a_26204/l_118581/"; minLength: 1)

Response

• @type string (default: "Bengo4Lawyer")
• id string required
• url string required
• name string nullable
• name_kana string nullable
• image string nullable
• images array (default: [])
• office_name string nullable
• postal_code string nullable
• address string nullable
• access string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• opening_hours array (default: [])
  • @type string (default: "Bengo4OpeningHours")
  • day string required
  • opens string nullable
  • closes string nullable
• policy_title string nullable
• policy_text string nullable
• practice_areas array (default: [])
  • @type string (default: "Bengo4PracticeArea")
  • id string nullable
  • name string required
  • headline string nullable
  • labels array (default: [])
  • details array (default: [])
    • @type string (default: "Bengo4PracticeDetail")
    • label string nullable
    • values array (default: [])
• introduction string nullable
• attributes array (default: [])
  • @type string (default: "Bengo4LabelValue")
  • label string required
  • value string nullable
• profile_sections array (default: [])
  • @type string (default: "Bengo4ProfileSection")
  • values array (default: [])
  • text string nullable
• office_details array (default: [])
  • @type string (default: "Bengo4LabelValue")
  • label string required
  • value string nullable
• price_lists array (default: [])
  • @type string (default: "Bengo4PriceList")
  • practice_area string required
  • entries array (default: [])
    • @type string (default: "Bengo4PriceItem")
    • label string nullable
    • text string nullable

Errors

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