/nice_bizinfo/companies/search

POST /api/nice_bizinfo/companies/search

Price: 20 credits

Search South Korean companies on NICE BizINFO by name, business or corporate registration number or representative name, or filter them by listing class, size, region, KSIC industry, revenue, operating profit and establishment date: name, registration numbers, representative, address, industry, class and size

How to use it

Use keyword for a known company and the filters to build a list; the two do not combine. Pass a result's id to nice_bizinfo/companies for the full profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 10000)
• keyword string nullable — Company name, business or corporate registration number, or representative name (examples: "삼성전자", "2208139938", "1301110006246"; minLength: 1)
• company_classes array nullable — Listing or legal class of the company (one of: "kospi", "kospi_managed", "kosdaq", "kosdaq_managed", "konex", "k_otc", "externally_audited", "general", "sole_proprietor", "public_institution", "non_profit", "merged", "closed", "other"; examples: ["kospi","kosdaq"])
• sizes array nullable — Company size class (one of: "large", "mid_sized", "small_medium", "other"; examples: ["large"])
• regions array nullable — Province or metropolitan city (one of: "seoul", "busan", "daegu", "incheon", "gwangju", "daejeon", "ulsan", "gyeonggi", "gangwon", "chungbuk", "chungnam", "jeonbuk", "jeonnam", "gyeongbuk", "gyeongnam", "jeju"; examples: ["seoul"])
• industry_code string nullable — Korean Standard Industrial Classification (KSIC) code (examples: "C", "C26", "J612")
• financial_year integer nullable — Fiscal year the revenue and operating profit bounds apply to (examples: 2025)
• revenue_min integer nullable — Lowest annual revenue, million KRW (examples: 1000000; min: 0)
• revenue_max integer nullable — Highest annual revenue, million KRW (examples: 2000000; min: 0)
• operating_profit_min integer nullable — Lowest annual operating profit, million KRW (examples: 100000; min: -100000000)
• operating_profit_max integer nullable — Highest annual operating profit, million KRW (examples: -1000; min: -100000000)
• established_after integer nullable — Earliest establishment day, unix seconds, day granular; a company with no establishment day on record is matched on its opening day instead (examples: 1577836800)
• established_before integer nullable — Latest establishment day, unix seconds, day granular; a company with no establishment day on record is matched on its opening day instead (examples: 1609372800)

Response

• @type string (default: "NiceBizinfoCompanySearchItem")
• id string required
• name string nullable
• name_en string nullable
• business_registration_number string nullable
• corporate_registration_number string nullable
• ceo string nullable
• address string nullable
• industry string nullable
• products string nullable
• company_class string nullable (one of: "kospi", "kospi_managed", "kosdaq", "kosdaq_managed", "konex", "k_otc", "externally_audited", "general", "sole_proprietor", "public_institution", "non_profit", "merged", "closed", "other")
• size string nullable (one of: "large", "mid_sized", "small_medium", "other")
• url string required

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.