/brreg/companies/sub_units

POST /api/brreg/companies/sub_units

Price: 5 credits

List the sub-units (business establishments / underenheter) of a Norwegian legal entity by its parent organization number. Each sub-unit includes name, organization form, location and postal addresses, industry codes, employee count and startup date.

How to use it

List all sub-units (business establishments) of a Norwegian company by its parent organization number (e.g. '923609016'). Use brreg/sub_units to fetch one sub-unit by its own organization number.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• organization_number string required — Parent organization number (9 digits) (examples: "923609016")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "BrregSubUnit")
• organization_number string required
• name string required
• parent_organization_number string nullable
• organization_form string nullable
• organization_form_description string nullable
• registration_date string nullable
• startup_date string nullable
• deregistered_date string nullable
• phone string nullable
• mobile string nullable
• email string nullable
• homepage string nullable
• employee_count integer nullable
• has_registered_employee_count boolean (default: false)
• location_address object nullable
  • @type string (default: "BrregAddress")
  • address array (default: [])
  • postal_code string nullable
  • city string nullable
  • municipality string nullable
  • municipality_number string nullable
  • country string nullable
  • country_code string nullable
• postal_address object nullable
  • @type string (default: "BrregAddress")
  • address array (default: [])
  • postal_code string nullable
  • city string nullable
  • municipality string nullable
  • municipality_number string nullable
  • country string nullable
  • country_code string nullable
• industry_code_1 object nullable
  • @type string (default: "BrregIndustryCode")
  • code string nullable
  • description string nullable
• industry_code_2 object nullable
  • @type string (default: "BrregIndustryCode")
  • code string nullable
  • description string nullable
• industry_code_3 object nullable
  • @type string (default: "BrregIndustryCode")
  • code string nullable
  • description string nullable
• auxiliary_code object nullable
  • @type string (default: "BrregIndustryCode")
  • code string nullable
  • description string nullable
• historic_names array (default: [])
  • @type string (default: "BrregHistoricName")
  • name string required
  • from_date string nullable
  • to_date string nullable
• registered_in_vat_register boolean (default: false)

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.