POST /api/kbo/companies
Price: 1 credit
Get a Belgian company's registry record from the Crossroads Bank for Enterprises (CBE/KBO/BCE) by its enterprise number: status, legal situation, start date, all registered names (with language), official abbreviation, registered seat address, contact details (phone, fax, email, web), entity type, legal form, number of establishment units, directors and other legal functions (role, name, since), entrepreneurial skills, characteristics (employer, VAT, registration), authorisations, NACE-BEL activity codes (VAT and NSSO, all versions), financial information (capital, annual assembly, financial year end) and links to related entities.
Look up one Belgian company by its enterprise number (e.g. '0202.239.951', accepts '0202239951'). Returns one item with enterprise_number, name, abbreviation, status, legal_situation, start_date, names, address, phone, fax, email, web, person_type, legal_form, establishment_unit_count, functions (role, name, since), entrepreneurial_skills, characteristics, authorisations, nace_codes (code, description, activity_type, version, since), capital, annual_assembly, financial_year_end and links (related entities). To find an enterprise number by company name, use kbo/companies/search; for its establishment units use kbo/companies/establishments.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)enterprise_number string required — Belgian enterprise number (CBE/KBO/BCE) (examples: "0202.239.951", "0202239951")@type string (default: "KboCompany")enterprise_number string requiredname string nullableabbreviation string nullablestatus string nullablelegal_situation string nullablelegal_situation_since string nullablestart_date string nullablenames array (default: [])@type string (default: "KboName")name string requiredlanguage string nullablesince string nullableaddress string nullableaddress_since string nullablephone string nullablefax string nullableemail string nullableweb string nullableperson_type string nullablelegal_form string nullablelegal_form_since string nullableestablishment_unit_count integer nullablefunctions array (default: [])@type string (default: "KboFunction")role string requiredname string requiredsince string nullableentrepreneurial_skills array (default: [])characteristics array (default: [])authorisations array (default: [])nace_codes array (default: [])@type string (default: "KboNaceCode")code string requireddescription string nullableactivity_type string requiredversion string requiredsince string nullablecapital string nullableannual_assembly string nullablefinancial_year_end string nullablelinks array (default: [])@type string (default: "KboRelatedEntity")enterprise_number string requiredname string nullablerelationship string nullablesince string nullableurl string required422 — 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 — No company found for the given enterprise 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.