/gcis/companies

POST /api/gcis/companies

Price: 1 credit

Get a Taiwan company's registry record by unified business number: name, status, capital, paid-in capital, par value and issued shares, responsible person, address, registration authority, founding, last-change and revocation dates, suspension period, registered business items and the directors and supervisors with their shareholdings

How to use it

Takes the unified business number; find one by name with gcis/companies/search. Branches of a company are listed by gcis/companies/branches, sole proprietorships are gcis/businesses.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tax_id string required — Unified business number (統一編號) of the company (examples: "22099131", "04541302")

Response

• @type string (default: "GcisCompany")
• tax_id string required
• name string nullable
• status string nullable
• status_code string nullable
• capital_twd number nullable
• paid_in_capital_twd number nullable
• par_value_twd number nullable
• issued_shares integer nullable
• responsible_person string nullable
• address string nullable
• registration_authority string nullable
• founded_date integer nullable
• last_change_date integer nullable
• revoked_date integer nullable
• suspension_status string nullable
• suspension_status_code string nullable
• suspension_approved_date integer nullable
• suspension_start_date integer nullable
• suspension_end_date integer nullable
• business_items array (default: [])
  • @type string (default: "GcisBusinessItem")
  • code string nullable
  • description string nullable
  • sequence integer nullable
• directors array (default: [])
  • @type string (default: "GcisDirector")
  • name string required
  • position string nullable
  • juristic_person string nullable
  • shares_held integer nullable

Errors

• 422 — tax_id is not an 8-character unified business number 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 company registered under that number 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.