get_entity

Get the current official Enhetsregister record for a 9-digit organisation number.

Signature: get_entity(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_entity/?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_entity?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_entity?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_entity?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_entity?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_entity",
  "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-26T04:04:17Z in 0.197 seconds.

_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/985586659
aktivitet:

1 results

  1. Callsenterforetak.
antallAnsatte:
130
epostadresse:
resepsjon@goexcellent.com
erIKonsern:
yes
forretningsadresse:
adresse:

1 results

  1. Kråkerøyveien 2B
kommune:
FREDRIKSTAD
kommunenummer:
3107
land:
Norge
landkode:
NO
postnummer:
1671
poststed:
KRÅKERØY
frivilligMvaRegistrertBeskrivelser:

1 results

  1. Utleier av bygg eller anlegg
harRegistrertAntallAnsatte:
yes
historiskeNavn:

8 results

  1. fraDato:
    2003-04-08 20:41:25
    navn:
    STARTSKUDDET 462 AS
    tilDato:
    2003-08-28 08:23:38
  2. fraDato:
    2003-08-28 14:10:32
    navn:
    EXCELLENT SNT NORWAY AS
    tilDato:
    2003-10-06 20:31:01
  3. fraDato:
    2003-10-06 20:31:01
    navn:
    EXCELLENT-SNT NORWAY AS
    tilDato:
    2004-09-29 20:31:07
  4. fraDato:
    2004-09-29 20:31:07
    navn:
    EXCELLENT NORWAY AS
    tilDato:
    2006-11-09 20:17:17
  5. fraDato:
    2006-11-09 20:17:17
    navn:
    TRADIMUS CUSTOMER SERVICES NORWAY AS
    tilDato:
    2007-08-14 20:33:21
  6. fraDato:
    2007-08-14 20:33:21
    navn:
    ADITRO CUSTOMER SERVICES NORWAY AS
    tilDato:
    2009-06-08 12:50:39
  7. fraDato:
    2009-06-08 12:50:39
    navn:
    GOEXCELLENT NORWAY AS
    tilDato:
    2016-09-17 14:40:23
  8. fraDato:
    2016-09-17 14:40:23
    navn:
    WEBHELP NORWAY AS
    tilDato:
    2024-10-09 21:11:34
hjemmeside:
www.webhelp.com/no
institusjonellSektorkode:
beskrivelse:
Private aksjeselskaper mv.
kode:
2100
kapital:
antallAksjer:
100
belop:
1300000.0
innfortDato:
2006-01-14
type:
Aksjekapital
valuta:
NOK
konkurs:
no
maalform:
Bokmål
naeringskode1:
beskrivelse:
Telefonvakttjenester og telefonsalg
kode:
82.200
navn:
CONCENTRIX NORWAY AS
organisasjonsform:
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
beskrivelse:
Aksjeselskap
kode:
AS
organization_id:
985586659
paategninger:

No results.

registreringsdatoAntallAnsatteEnhetsregisteret:
2026-09-14
registreringsdatoAntallAnsatteNAVAaregisteret:
2026-09-10
registreringsdatoEnhetsregisteret:
2003-04-08
registreringsdatoForetaksregisteret:
2003-04-08
registreringsdatoFrivilligMerverdiavgiftsregisteret:
2014-01-28
registreringsdatoMerverdiavgiftsregisteret:
2003-01-01
registreringsdatoMerverdiavgiftsregisteretEnhetsregisteret:
2003-11-12
registrertIForetaksregisteret:
yes
registrertIFrivillighetsregisteret:
no
registrertIMvaregisteret:
yes
registrertIPartiregisteret:
no
registrertIStiftelsesregisteret:
no
respons_klasse:
Enhet
sisteInnsendteAarsregnskap:
2025
stiftelsesdato:
2003-02-28
telefon:
21 01 01 21
underAvvikling:
no
underTvangsavviklingEllerTvangsopplosning:
no
vedtektsdato:
2024-08-14
vedtektsfestetFormaal:

4 results

  1. Selv, eller gjennom hel- eller deleide selskaper eller ved andre
  2. virksomheter på det nordiske markedet via telefon og andre
  3. kommunikasjonsmedia å forestå produktinformasjon, kundeservice, salg
  4. og annen virksomhet beslektet med denne.
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_entity 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.