/houjinbangou/invoice_issuers/changes

POST /api/houjinbangou/invoice_issuers/changes

Price: 20 credits

List daily changes to Japan's qualified invoice issuer register (適格請求書発行事業者) over the last 40 business days, newest publication day first: new registrations, updates, expiries, revocations and deletions, with the issuer's number, kind, residency, name, dates and addresses

How to use it

Covers the 40 most recent publication days; older dates return nothing. Rows of individuals carry no name; pass registration_number to houjinbangou/invoice_issuers for the published record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• date_from integer nullable — Earliest publication day, unix seconds (examples: 1788393600)
• date_to integer nullable — Latest publication day, unix seconds (examples: 1790985600)
• change_types array nullable — Kinds of change to keep (one of: "registered", "updated", "expired", "revoked", "deleted"; examples: ["registered","revoked"])
• kind string nullable — Keep only individuals or only legal entities (one of: "individual", "legal_entity")
• count integer required — Max number of results (min: 1; max: 100000)

Response

• @type string (default: "HoujinbangouInvoiceIssuerChange")
• registration_number string required
• published_date integer required
• sequence_number integer nullable
• change_type string required
• is_correction boolean (default: false)
• kind string nullable
• residency string nullable
• is_latest boolean (default: false)
• name string nullable
• kana string nullable
• registration_date integer nullable
• update_date integer nullable
• revocation_date integer nullable
• expiry_date integer nullable
• address string nullable
• address_prefecture_code string nullable
• address_city_code string nullable
• published_address string nullable
• published_address_prefecture_code string nullable
• published_address_city_code string nullable
• domestic_office_address string nullable
• domestic_office_prefecture_code string nullable
• domestic_office_city_code string nullable

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 — 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.