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-26T22:30:39Z in 0.174 seconds.

_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/960317114/roller
enhet:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/960317114
rollegrupper:

4 results

  1. roller:

    1 results

    1. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1975-05-03
      navn:
      etternavn:
      Berge
      fornavn:
      Aina Marianne
      rekkefolge:
      0
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/DAGL
      beskrivelse:
      Daglig leder
      kode:
      DAGL
    sistEndret:
    2019-05-27
    type:
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/DAGL
    beskrivelse:
    Daglig leder
    kode:
    DAGL
  2. roller:

    6 results

    1. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1945-08-23
      navn:
      etternavn:
      Pedersen
      fornavn:
      Vigdis
      rekkefolge:
      0
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/LEDE
      beskrivelse:
      Styrets leder
      kode:
      LEDE
    2. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1952-04-18
      navn:
      etternavn:
      Sætre
      fornavn:
      Stig
      rekkefolge:
      1
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      beskrivelse:
      Styremedlem
      kode:
      MEDL
    3. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1938-06-07
      navn:
      etternavn:
      Dager
      fornavn:
      Wenche
      rekkefolge:
      2
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      beskrivelse:
      Styremedlem
      kode:
      MEDL
    4. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1982-06-24
      navn:
      etternavn:
      Myhre
      fornavn:
      Hege Merete
      rekkefolge:
      3
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      beskrivelse:
      Styremedlem
      kode:
      MEDL
    5. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1989-03-16
      navn:
      etternavn:
      Bastas
      fornavn:
      Yusuf Nebi
      rekkefolge:
      4
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      beskrivelse:
      Styremedlem
      kode:
      MEDL
    6. avregistrert:
      no
      person:
      erDoed:
      no
      fodselsdato:
      1976-09-13
      navn:
      etternavn:
      Standal
      fornavn:
      Torgeir
      mellomnavn:
      Ambriz
      rekkefolge:
      5
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
      beskrivelse:
      Styremedlem
      kode:
      MEDL
      valgtAv:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/representanter/AREP
      beskrivelse:
      Representant for de ansatte
      kode:
      AREP
    sistEndret:
    2026-02-10
    type:
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/STYR
    beskrivelse:
    Styre
    kode:
    STYR
  3. roller:

    1 results

    1. avregistrert:
      no
      enhet:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/enheter/874903302
      erSlettet:
      no
      godkjenningsstatus:
      Godkjent revisjonsforetak
      navn:

      1 results

      1. KNUDSEN REVISJONSBYRÅ AS
      organisasjonsform:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
      beskrivelse:
      Aksjeselskap
      kode:
      AS
      organization_id:
      874903302
      rekkefolge:
      0
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/REVI
      beskrivelse:
      Revisor
      kode:
      REVI
    sistEndret:
    1999-01-08
    type:
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/REVI
    beskrivelse:
    Revisor
    kode:
    REVI
  4. roller:

    1 results

    1. avregistrert:
      no
      enhet:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/enheter/982297338
      erSlettet:
      no
      godkjenningsstatus:
      Godkjent regnskapsforetak
      navn:

      1 results

      1. T-RYGG REGNSKAPSBYRÅ
      organisasjonsform:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/ENK
      beskrivelse:
      Enkeltpersonforetak
      kode:
      ENK
      organization_id:
      982297338
      rekkefolge:
      0
      type:
      _links:
      self:
      href:
      https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/REGN
      beskrivelse:
      Regnskapsfører
      kode:
      REGN
    sistEndret:
    2006-10-25
    type:
    _links:
    self:
    href:
    https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/REGN
    beskrivelse:
    Regnskapsfører
    kode:
    REGN
limit:
25
offset:
0
returned:
4
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.