/gcis/companies/search

POST /api/gcis/companies/search

Price: 20 credits

Search Taiwan companies by text contained in the registered name, within one registration status: unified business number, name, status, capital, paid-in capital, responsible person, address, registration authority, founding and last-change dates

How to use it

Matches the query anywhere in the Chinese registered name, in unified-business-number order. Pass tax_id to gcis/companies for directors and business items.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Text contained in the company name (examples: "台積", "鴻海精密")
• status string — Registration status of the companies (default: "active"; one of: "active", "active_ordered_to_dissolve", "reorganization", "dissolved", "revoked", "bankrupt", "dissolved_by_merger", "registration_withdrawn", "abolished", "registration_abolished", "dissolved_liquidated", "revoked_liquidated", "abolished_liquidated", "registration_revoked", "dissolved_by_split", "bankruptcy_terminated", "bankruptcy_annulled", "bankruptcy_concluded", "bankruptcy_concluded_liquidating", "bankruptcy_liquidated", "receivership", "revoked_without_liquidation", "permit_revoked", "permit_abolished", "winding_up", "incorporation_revoked", "winding_up_completed")
• count integer required — Max number of companies to return (min: 1; max: 10000)

Response

• @type string (default: "GcisCompanySearchItem")
• tax_id string required
• name string nullable
• status string nullable
• status_code string nullable
• capital_twd number nullable
• paid_in_capital_twd number nullable
• responsible_person string nullable
• address string nullable
• registration_authority string nullable
• registration_authority_code string nullable
• founded_date integer nullable
• last_change_date integer nullable

Errors

• 422 — query is blank or status is not a listed value 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.