POST /api/brreg/sub_units/search
Price: 5 credits
Search Norwegian sub-units (business establishments) in the Central Coordinating Register by name and filters: organization number, parent organization, organization form, NACE industry code, municipality, employee count range, registration date range and VAT registration. Returns the same record shape as brreg/sub_units.
Search Norwegian sub-units (business establishments) by name and optional filters (parent organization, organization_form, industry_code, municipality_number, employee count range). Use brreg/companies/sub_units to list all sub-units of a specific parent company.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)name string nullable — Sub-unit name to search for (examples: "Equinor")organization_number string nullable — Filter by organization numberparent_organization_number string nullable — Filter by parent organization number (examples: "923609016")organization_form string nullable — Filter by organization form (one of: "AAFY", "ADOS", "ANNA", "ANS", "AS", "ASA", "BA", "BBL", "BEDR", "BO", "BRL", "DA", "ENK", "EOFG", "ESEK", "FKF", "FLI", "FYLK", "GFS", "IKJP", "IKS", "KBO", "KF", "KIRK", "KOMM", "KS", "KTRF", "NUF", "OPMV", "ORGL", "PERS", "PK", "PRE", "SA", "SAM", "SE", "SF", "SPA", "STAT", "STI", "SÆR", "TVAM", "UTLA", "VPFO"; examples: "BEDR")industry_code string nullable — Filter by NACE industry code (examples: "62.01", "06.100")municipality_number string nullable — Filter by municipality number (examples: "1103")from_employee_count integer nullable — Minimum number of employees (min: 0)to_employee_count integer nullable — Maximum number of employees (min: 0)from_registration_date string nullable — Earliest registration date (YYYY-MM-DD) (examples: "2020-01-01")to_registration_date string nullable — Latest registration date (YYYY-MM-DD) (examples: "2024-12-31")registered_in_vat_register boolean nullable — Filter by registration in the VAT registercount integer required — Max number of results (min: 1)@type string (default: "BrregSubUnit")organization_number string requiredname string requiredparent_organization_number string nullableorganization_form string nullableorganization_form_description string nullableregistration_date string nullablestartup_date string nullablederegistered_date string nullablephone string nullablemobile string nullableemail string nullablehomepage string nullableemployee_count integer nullablehas_registered_employee_count boolean (default: false)location_address object nullable@type string (default: "BrregAddress")address array (default: [])postal_code string nullablecity string nullablemunicipality string nullablemunicipality_number string nullablecountry string nullablecountry_code string nullablepostal_address object nullable@type string (default: "BrregAddress")address array (default: [])postal_code string nullablecity string nullablemunicipality string nullablemunicipality_number string nullablecountry string nullablecountry_code string nullableindustry_code_1 object nullable@type string (default: "BrregIndustryCode")code string nullabledescription string nullableindustry_code_2 object nullable@type string (default: "BrregIndustryCode")code string nullabledescription string nullableindustry_code_3 object nullable@type string (default: "BrregIndustryCode")code string nullabledescription string nullableauxiliary_code object nullable@type string (default: "BrregIndustryCode")code string nullabledescription string nullablehistoric_names array (default: [])@type string (default: "BrregHistoricName")name string requiredfrom_date string nullableto_date string nullableregistered_in_vat_register boolean (default: false)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.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.