/brreg/companies/roles

POST /api/brreg/companies/roles

Price: 1 credit

Get the registered roles (board members, CEO, auditor, etc.) of a Norwegian legal entity by its organization number. Each role includes the role group and type, the person (name, birth date) or the company holding it, and whether the role has been deregistered.

How to use it

List the people and companies holding registered roles in a Norwegian company by its organization number (e.g. board members, CEO, auditor). Each item has group, type, person or company, and order.

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 — Norwegian organization number (9 digits) (examples: "923609016")

Response

• @type string (default: "BrregRole")
• group string nullable
• group_description string nullable
• type string nullable
• type_description string nullable
• person object nullable
  • @type string (default: "BrregRolePerson")
  • first_name string nullable
  • middle_name string nullable
  • last_name string nullable
  • name string nullable
  • birth_date string nullable
  • is_dead boolean (default: false)
• company object nullable
  • @type string (default: "BrregRoleCompany")
  • organization_number string nullable
  • name string nullable
  • organization_form string nullable
  • is_deleted boolean (default: false)
• deregistered boolean (default: false)
• order integer nullable

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 — No legal entity found for the given organization 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.

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.