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.

Parameter	Requirement	JSON type	Description
`organization_id`	required	string
`limit`	optional	integer	Gateway page size; default 25, maximum 100.
`offset`	optional	integer	Number 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.

Result

Source: Brønnøysund Register Centre. Retrieved 2026-09-24T21:24:19Z in 0.191 seconds.

rollegrupper:

1 results

type:
kode:
STYR
beskrivelse:
Styre
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/roller/rollegruppetyper/STYR
sistEndret:
2026-02-17
roller:
9 results
1. type:
  kode:
  LEDE
  beskrivelse:
  Styrets leder
  _links:
  self:
  href:
  https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/LEDE
  person:
  fodselsdato:
  1986-07-17
  navn:
  fornavn:
  Linn
  mellomnavn:
  Rastad
  etternavn:
  Sander
  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:
  1968-08-23
  navn:
  fornavn:
  Kari Irene
  mellomnavn:
  Indgjerd
  etternavn:
  Holter
  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:
  1967-09-24
  navn:
  fornavn:
  Unni Annette
  etternavn:
  Mundal
  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:
  1972-10-09
  navn:
  fornavn:
  Odd Arne
  etternavn:
  Sønsterud
  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:
  1988-03-30
  navn:
  fornavn:
  Bjørn-Terje
  mellomnavn:
  Eiken
  etternavn:
  Nedreberg
  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-09
  navn:
  fornavn:
  Tone Elisabeth
  etternavn:
  Vestli
  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:
  1966-09-12
  navn:
  fornavn:
  Tor Arne
  etternavn:
  Rygg
  erDoed:
  no
  avregistrert:
  no
  rekkefolge:
  6
8. type:
  kode:
  MEDL
  beskrivelse:
  Styremedlem
  _links:
  self:
  href:
  https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
  person:
  fodselsdato:
  1977-04-11
  navn:
  fornavn:
  Line
  etternavn:
  Lerdalen
  erDoed:
  no
  avregistrert:
  no
  rekkefolge:
  7
9. type:
  kode:
  MEDL
  beskrivelse:
  Styremedlem
  _links:
  self:
  href:
  https://data.brreg.no/enhetsregisteret/api/roller/rolletyper/MEDL
  person:
  fodselsdato:
  1950-08-21
  navn:
  fornavn:
  Ellen
  mellomnavn:
  Sogge
  etternavn:
  Røtnes
  erDoed:
  no
  avregistrert:
  no
  rekkefolge:
  8

_links:

self:

href:: https://data.brreg.no/enhetsregisteret/api/enheter/993328200/roller

enhet:

href:: https://data.brreg.no/enhetsregisteret/api/enheter/993328200

limit:

offset:

returned:

has_more_results:

truncated:

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

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
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

Confirm the organization number before detail lookups. Use the canonical company page to combine owners, roles, grants, Doffin and jobs.

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.

AI agent? Read the complete navigation and programming guide.