/houjinbangou/invoice_issuers/batch

POST /api/houjinbangou/invoice_issuers/batch

Price: 5 credits

Check up to 100 Japanese qualified invoice issuer registration numbers at once against the National Tax Agency register: whether each number is registered, the issuer's name and kana reading, and whether the registration was revoked or expired or belongs to a foreign business

How to use it

One row per distinct input number, in input order; is_found is false for numbers that are not registered. For dates, address and history pass a number to houjinbangou/invoice_issuers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• registration_numbers array required — Qualified invoice issuer registration numbers (examples: ["T1180301018771","T2110001004111","1810013196420"]; minItems: 1; maxItems: 100)

Response

• @type string (default: "HoujinbangouInvoiceIssuerCheck")
• registration_number string required
• is_found boolean required
• name string nullable
• kana string nullable
• is_revoked boolean (default: false)
• is_expired boolean (default: false)
• is_foreign boolean (default: false)
• url string nullable

Errors

• 422 — A 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 — 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.