/houjinbangou/invoice_issuers

POST /api/houjinbangou/invoice_issuers

Price: 1 credit

Get a Japanese qualified invoice issuer (適格請求書発行事業者) from the National Tax Agency register by its registration number: name, kana reading of foreign names, registration, expiry and revocation dates, head-office address, domestic office of a foreign business, last update date and the registration history

How to use it

corporate_number is set for corporations and associations, whose registration number is T plus their Corporate Number; pass it to houjinbangou/companies for the company record. Individuals who did not ask to publish an address come back without one.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• registration_number string required — Qualified invoice issuer registration number (examples: "T1180301018771", "1180301018771")

Response

• @type string (default: "HoujinbangouInvoiceIssuer")
• registration_number string required
• corporate_number string nullable
• name string required
• kana string nullable
• registration_date integer nullable
• expiry_date integer nullable
• revocation_date integer nullable
• address string nullable
• domestic_office_address string nullable
• last_updated_date integer nullable
• history array (default: [])
  • @type string (default: "HoujinbangouInvoiceHistoryEvent")
  • number integer required
  • event string required
  • date integer nullable
  • is_new_registration boolean (default: false)
• url string required

Errors

• 422 — The registration number is not T followed by 13 digits or its check digit does not match 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 invoice issuer is registered under that number, including numbers removed from the register 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.