/gcis/business-items

POST /api/gcis/business-items

Price: 10 credits

Look up Taiwan's business item codes (營業項目代碼) used in company and business registrations: code, name, definition, category, class and subclass, and the matching standard industrial classification codes

How to use it

With no code and no query the whole code table is listed. The codes match business_items[].code returned by gcis/companies and gcis/businesses.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• code string nullable — Business item code or the leading part of one (examples: "CC01080", "F2", "I")
• query string nullable — Text contained in the item code, name or definition (examples: "電子", "顧問")
• count integer required — Max number of items to return (min: 1; max: 1000)

Response

• @type string (default: "GcisBusinessItemDefinition")
• code string required
• name string nullable
• definition string nullable
• category_code string nullable
• category string nullable
• division_code string nullable
• division string nullable
• group_code string nullable
• group string nullable
• industry_classes array (default: [])
  • @type string (default: "GcisIndustryClass")
  • code string required
  • name string nullable

Errors

• 422 — code is not a business item code or query is blank 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 business item under that full 7-character code 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.