/mhlw_labour_violations/cases/search

POST /api/mhlw_labour_violations/cases/search

Price: 10 credits

Search the cases of labour-standards law violations that Japan's prefectural labour bureaus referred to prosecutors and published over the last 12 months: company or workplace name, address, labour bureau, publication date, violated law articles, case summary, referral and outcome dates

How to use it

Results follow the ministry's list order, bureau by bureau from Hokkaido to Okinawa. Names are as printed in the list, company forms abbreviated, so search a distinctive part of the name.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company_name string nullable — Text the company or workplace name contains (examples: "建設", "運輸")
• prefecture string nullable — Prefecture of the labour bureau that published the case (one of: "hokkaido", "aomori", "iwate", "miyagi", "akita", "yamagata", "fukushima", "ibaraki", "tochigi", "gunma", "saitama", "chiba", "tokyo", "kanagawa", "niigata", "toyama", "ishikawa", "fukui", "yamanashi", "nagano", "gifu", "shizuoka", "aichi", "mie", "shiga", "kyoto", "osaka", "hyogo", "nara", "wakayama", "tottori", "shimane", "okayama", "hiroshima", "yamaguchi", "tokushima", "kagawa", "ehime", "kochi", "fukuoka", "saga", "nagasaki", "kumamoto", "oita", "miyazaki", "kagoshima", "okinawa")
• law string nullable — Text the violated law articles contain (examples: "労働基準法第32条", "最低賃金法")
• keyword string nullable — Text the case summary contains (examples: "墜落", "賃金")
• date_from integer nullable — Earliest publication day, unix seconds (examples: 1756684800)
• date_to integer nullable — Latest publication day, unix seconds (examples: 1788134400)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "MhlwLabourViolationCase")
• id string required
• company_name string required
• address string nullable
• prefecture string nullable
• labour_bureau string required
• published_date integer nullable
• laws array (default: [])
• summary string nullable
• referred_date integer nullable
• events array (default: [])
  • @type string (default: "MhlwLabourViolationCaseEvent")
  • date integer nullable
  • event string required
• notes string nullable
• page integer required
• pdf_url string required

Errors

• 422 — date_from is after date_to 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 — The entity was not found, or a precondition failed 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.