/gcis/changes

POST /api/gcis/changes

Price: 5 credits

List Taiwan registry events of one kind by approval day: new companies, company changes, company dissolutions, branch abolitions, business closures or limited-partnership dissolutions, each with the unified business number, name and status

How to use it

Days are walked from date_to back to date_from, newest first. Pass tax_id to gcis/companies or gcis/businesses for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• feed string required — Kind of registration event (one of: "company_setup", "company_change", "company_dissolution", "branch_abolition", "business_closure", "partnership_dissolution")
• date_from integer required — First day of the window, unix seconds (examples: 1788220800)
• date_to integer nullable — Last day of the window, unix seconds; the first day alone when omitted
• count integer required — Max number of records to return (min: 1; max: 10000)

Response

• @type string (default: "GcisChange")
• tax_id string required
• feed string required (one of: "company_setup", "company_change", "company_dissolution", "branch_abolition", "business_closure", "partnership_dissolution")
• change_date integer required
• name string nullable
• status string nullable
• branch_tax_id string nullable
• branch_name string nullable
• registration_authority string nullable

Errors

• 422 — feed is not a listed value, date_to is before date_from or the window spans over 31 days 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.