/mlit_etsuran/contractors

POST /api/mlit_etsuran/contractors

Price: 1 credit

Get a Japanese construction contractor (建設業者) from the national licence register by its licence id: permit authority and number, name and kana, representative, head-office address and phone, legal form, capital, other businesses, the licensed construction trades with their general or special grade, and each permit's date, validity period, conditions and trades

How to use it

Take id from license_id of mlit_etsuran/contractors/search. capital is in yen. trades lists every trade the contractor holds; permits splits them by permit date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Contractor licence id: the permit authority code followed by the six-digit permit number (examples: "01552826", "00015069"; pattern: ^\d{8}$)

Response

• @type string (default: "MlitEtsuranContractor")
• id string required
• authority string nullable
• license_number string required
• name string required
• name_kana string nullable
• representative string nullable
• representative_kana string nullable
• postal_code string nullable
• address string nullable
• phone string nullable
• legal_form string nullable
• capital number nullable
• has_other_business boolean nullable
• trades array (default: [])
  • @type string (default: "MlitEtsuranTrade")
  • trade string required
  • grade string required
• permits array (default: [])
  • @type string (default: "MlitEtsuranPermit")
  • permit_date integer nullable
  • valid_from integer nullable
  • valid_to integer nullable
  • conditions string nullable
  • trades array (default: [])
    • @type string (default: "MlitEtsuranTrade")
    • trade string required
    • grade string required

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 — No contractor is licensed 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.