get_roles

Get public role groups registered for an entity.

Signature: get_roles(organization_id: string, required; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/brreg/get_roles/?organization_id={organization_id}&limit=25&offset=0

Replace {organization_id} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_roles?organization_id={organization_id}&limit=25&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
organization_idrequiredstring
limitoptionalintegerGateway page size; default 25, maximum 100.
offsetoptionalintegerNumber of list items to skip; default 0.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_roles?organization_id={organization_id}&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_roles?organization_id={organization_id}&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_roles?organization_id={organization_id}&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "brreg",
  "operation": "get_roles",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string

Result

Source: Brønnøysund Register Centre. Retrieved 2026-09-11T10:03:22Z in 0.154 seconds.

rollegrupper:

3 results

  1. type:
    kode:
    STYR
    beskrivelse:
    Styre
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/STYR
    sistEndret:
    2021-01-18
    roller:

    7 results

    1. type:
      kode:
      LEDE
      beskrivelse:
      Styrets leder
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/LEDE
      person:
      fodselsdato:
      1979-04-08
      navn:
      fornavn:
      Erling
      etternavn:
      Strøm
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      0
    2. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1965-12-02
      navn:
      fornavn:
      Øyvind
      mellomnavn:
      Rosmer
      etternavn:
      Berg
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      1
    3. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1965-04-03
      navn:
      fornavn:
      Bård Arnstein
      etternavn:
      Haga
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      2
    4. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1975-11-03
      navn:
      fornavn:
      Glenn Tomas
      etternavn:
      Bjørnsrud
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      3
    5. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1969-10-11
      navn:
      fornavn:
      Fredrik
      etternavn:
      Syvertsen
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      4
    6. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1966-01-16
      navn:
      fornavn:
      Knut
      etternavn:
      Nilsen
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      5
    7. type:
      kode:
      MEDL
      beskrivelse:
      Styremedlem
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      person:
      fodselsdato:
      1962-11-23
      navn:
      fornavn:
      Per-Anton
      etternavn:
      Schrøder
      erDoed:
      no
      avregistrert:
      no
      rekkefolge:
      6
  2. type:
    kode:
    REVI
    beskrivelse:
    Revisor
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/REVI
    sistEndret:
    2021-01-18
    roller:

    1 results

    1. type:
      kode:
      REVI
      beskrivelse:
      Revisor
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/REVI
      enhet:
      organization_id:
      976389387
      organisasjonsform:
      kode:
      AS
      beskrivelse:
      Aksjeselskap
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
      navn:

      1 results

      1. ERNST & YOUNG AS
      godkjenningsstatus:
      Godkjent revisjonsforetak
      erSlettet:
      no
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/enheter/976389387
      avregistrert:
      no
      rekkefolge:
      0
  3. type:
    kode:
    REGN
    beskrivelse:
    Regnskapsfører
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/REGN
    sistEndret:
    2021-05-19
    roller:

    1 results

    1. type:
      kode:
      REGN
      beskrivelse:
      Regnskapsfører
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/REGN
      enhet:
      organization_id:
      913397460
      organisasjonsform:
      kode:
      AS
      beskrivelse:
      Aksjeselskap
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
      navn:

      1 results

      1. NORDIC ACCOUNTING AS
      godkjenningsstatus:
      Godkjent regnskapsforetak
      erSlettet:
      no
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/enheter/913397460
      avregistrert:
      no
      rekkefolge:
      0
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/925856487/roller
enhet:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/925856487
limit:
25
offset:
0
returned:
3
has_more_results:
no
truncated:
no
Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the get_roles lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.