Documentation for Open Data from the Central Coordinating Register for Legal Entities (CCR) (2.0.0)

Central Coordinating Register for Legal Entities (CCR)

A registry of basic data about legal persons and other entities. The CCR assigns organisation numbers for unique identification of entities.

Organisation Number

Nine-digit number that uniquely identifies entities in the CCR.

Entity

The top-level unit in the registration structure of the CCR.
Examples include sole proprietorships, associations, companies, condominiums, and others that are registered in the CCR.
Identified by organisation number.

Sub-entity

The lowest level unit in the registration structure of the CCR.
A sub-entity cannot exist alone and is always connected to a main unit.
Identified by organisation number.

Type of organisation

The formal organisation of a business, which provides guidelines regarding liability, taxes, audit obligations, rights and obligations.

Industrial Code

Some businesses have both a standard industrial code and a support unit code.
In these cases, the standard industrial codes should be presented first with code and text.
The support unit code is then shown as text, without a code - with the addition of the text "Provides services to its own group."

Example:

11.050 Production of beer
11.070 Production of mineral waters, soft drinks, and other bottled waters

Wholesale of beverages otherwise:
Provides services to its own group

See Industrial codes at brreg.no
Standard for Business Grouping can be found at ssb.no

Municipality and Geographical Area Division

The entity's business address, postal address, or location address is linked to a municipality or a geographical area division.
From January 1, 2019, the areas Spitsbergen, Bjørnøya, and Hopen will be included in the geographical area division Svalbard area, with code 2100.

Overview of municipalities and geographical area divisions can be found at Standard for Municipal Division and Standard for Regional Special Codes from SSB.

Cadastral Unit

An object that is registered as a unit in the cadastre.
Such cadastral units are primarily land properties, designated by land number and property units number, condominiums, or leasehold.

Support Unit

Support units are entities that only provide group- or enterprise-internal services and are classified with the same industrial code as the units they serve.
They are assigned an alternative industrial code - support unit code - which indicates the type of service performed.

Role

Roles refer to the relationships an entity can have with natural persons or other entities in the CCR.

Role Type

Code list/enum.
Role type further describes the role object.
The fields in the object can vary for different role types.

Examples:

INNH (sole proprietor) registered as a person with a date of birth in a sole proprietorship.
REVI (auditor) registered as an entity with an organisation number.

Role Group

A role group is a logical collection of roles that can be grouped together.

Role Group Type

Code list/enum.
A role group type tells which roles are included in a role group.

For example:

BOARD is a role group for these roles: Chair of the board, deputy chair of the board, board member, deputy board member, and observer.

Representative

Code list/enum.
Representative shows whom the person represents on the board. It can be either the employees, A-, B-, or C-shareholders.

Most services respond with JSON, in the HAL format (Hypertext Application Language). The exception is the download services, which result in GZIP-compressed JSON without HAL.

See more about versioning in the section on Versioning.

404 Not Found

If you make a request to an endpoint where the resource does not exist, even though the request is valid, you will receive a response with status 404 and no content.

400 Invalid Request

All endpoints have common validation for parameters.
If one or more parameters have an invalid value, you will receive a response with status code 400.
All invalid parameters will be listed, with an explanation of why.
Below is an example of a 400 response, with an invalid value for the organisation number.

    HTTP/1.1 400 Bad Request
    Vary: Origin
    Vary: Access-Control-Request-Method
    Vary: Access-Control-Request-Headers
    Content-Type: application/json
    Content-Length: 367
    {
      "timestamp" : 1622200011303,
      "status" : 400,
      "error" : "Invalid request",
      "path" : "/enhetsregisteret/api/enheter/9ECD01011/roller",
      "errorCount" : 1,
      "validationErrors" : [ {
        "errorMessage" : "The organisation number must be a number with exactly 9 digits",
        "parameters" : [ "9ECD01011" ],
        "incorrectValue" : "9ECD01011"
      } ]
    }
    

500 Server Error

All endpoints have common error handling for unexpected errors. If an error occurs, you will receive a response with status code 500.
If you wish to report the error to us, it would be helpful if you also send us the trace from the response. This is a UUID that makes it easier for us to locate the logs from the failed request.
Below is an example of a 500 response:

    HTTP/1.1 500 Internal Server Error
    Vary: Origin
    Vary: Access-Control-Request-Method
    Vary: Access-Control-Request-Headers
    Content-Type: application/json
    Content-Length: 257 
    {
      "timestamp" : "2021-05-28T11:34:33.435+0000",
      "status" : 500,
      "error" : "Internal Server Error",
      "message" : "Internal Server Error",
      "path" : "/enhetsregisteret/api/enheter/999999999/roller",
      "trace" : "5631709a-6e3e-4b72-94e7-fcbf6341272a"
    }
    

May 5, 2025

Endpoints

/api/enheter
/frivillighetsregisteret/api/frivillige-organisasjoner
/frivillighetsregisteret/api/frivillige-organisasjoner/{organisasjonsnummer}
/frivillighetsregisteret/api/frivillige-organisasjoner/totalbestand/csv
/frivillighetsregisteret/api/icnpo-kategorier
/frivillighetsregisteret/api/informasjonstyper

Changes

• Add new query parameters:
  • /api/enheter:
    • "underKonkursbehandling": Search for organisations that are under bankruptcy, compulsory liquidation, or dissolution.
• Add new endpoints:
  • /frivillighetsregisteret/api/frivillige-organisasjoner
  • /frivillighetsregisteret/api/frivillige-organisasjoner/{organisasjonsnummer}
  • /frivillighetsregisteret/api/frivillige-organisasjoner/totalbestand/csv
  • /frivillighetsregisteret/api/icnpo-kategorier
  • /frivillighetsregisteret/api/informasjonstyper

February 26, 2025

Endpoints

/api/enheter
/api/enheter/{orgnr}
/api/enheter/lastned
/api/enheter/lastned/csv
/api/enheter/lastned/regneark
/api/underenheter

Changes

• Add new response fields in JSON, CSV, Excel, and API
  • paategninger (in Excel and CSV, this will be represented as YES/NO)
  • registreringsnummerIHjemland (applies to type of organisation UTLA)
• Add new query parameters
  • /api/enheter:
    • "navnMetodeForSoek": Search method for the navn parameter. The only supported value is FORTLOEPENDE. Example usage: navn=sesam stasjon&navnMetodeForSoek=FORTLOEPENDE
  • /api/underenheter:
    • "navnMetodeForSoek": Search method for the navn parameter. The only supported value is FORTLOEPENDE. Example usage: navn=sesam stasjon&navnMetodeForSoek=FORTLOEPENDE

October 5, 2024

Endpoints

/api/enheter
/api/enheter/{orgnr}
/api/enheter/lastned
/api/enheter/lastned/regneark
/api/underenheter
/api/underenheter/{orgnr}
/api/underenheter/lastned
/api/underenheter/lastned/regneark

Changes

• Remove V1 from search and total stock endpoints.

October 3, 2024

Endpoints

/api/enheter
/api/underenheter
/partiregisteret/api/lastned/csv
/frivillighetsregisteret/api/lastned/csv

Changes

• Add new response fields in json, csv, excel and api
  • /api/enheter:
    • epostadresse
    • telefon
    • mobil
    • registreringsdatoForetaksregisteret
    • registreringsdatoFrivillighetsregisteret
    • registreringsdatoMerverdiavgiftsregisteret
    • registreringsdatoMerverdiavgiftsregisteretEnhetsregisteret
    • registreringsdatoFrivilligMerverdiavgiftsregisteret
    • registreringsdatoPartiregisteret
    • registrertIPartiregisteret
    • registreringsdatoAntallAnsatteNAVAaregisteret
    • registreringsdatoAntallAnsatteEnhetsregisteret
  • /api/underenheter
    • epostadresse
    • telefon
    • mobil
    • registreringsdatoMerverdiavgiftsregisteret
    • registreringsdatoMerverdiavgiftsregisteretEnhetsregisteret
    • registreringsdatoFrivilligMerverdiavgiftsregisteret
    • registreringsdatoAntallAnsatteNAVAaregisteret
    • registreringsdatoAntallAnsatteEnhetsregisteret
• Add new query parameters
  • /api/enheter:
    • "fraRegistreringsdatoMerverdiavgiftsregisteret". Filter entities on earliest registration date in the VAT register.
    • "tilRegistreringsdatoMerverdiavgiftsregisteret". Filter entities on latest registration date in the VAT register.
    • "fraRegistreringsdatoForetaksregisteret". Filter entities on earliest registration date in the Register of Business Enterprises.
    • "tilRegistreringsdatoForetaksregisteret". Filter entities on latest registration date in the Register of Business Enterprises.
    • "fraRegistreringsdatoFrivillighetsregisteret". Filter entities on earliest registration date in the Register of Non-Profit Organisations.
    • "tilRegistreringsdatoFrivillighetsregisteret". Filter entities on latest registration date in the Register of Non-Profit Organisations.
    • "fraRegistreringsdatoPartiregisteret". Filter entities on earliest registration date in the Register of Political Parties.
    • "tilRegistreringsdatoPartiregisteret". Filter entities on latest registration date in the Register of Political Parties.
    • "registrertIPartiregisteret": Filter entities that are registered in the Register of Political Parties.
  • /api/underenheter:
    • "fraRegistreringsdatoMerverdiavgiftsregisteret". Filter entities on earliest registreringsdato i VAT register.
    • "tilRegistreringsdatoMerverdiavgiftsregisteret". Filter entities on latest registreringsdato i VAT register.
• Add new endpoints for download of total inventory
  • /partiregisteret/api/lastned/csv
  • /frivillighetsregisteret/api/lastned/csv
    • Total inventory from the Register of Non-Profit Organisations is temporarily available and will be replaced by a new services in spring/autom 2025.

July 4, 2024

Endpoints

/api/enheter/lastned/csv
/api/underenheter/lastned/csv

Changes

• Replace /n with line breaks in forretningsadresse.adresse, beliggenhetsadresse.adresse og postadresse.adresse

June 17, 2024

Endpoints

/autorisert-api/enheter/{orgnr}/roller

Changes

• New endpoint for retrieving roles that includes personal identification numbers. This endpoint is secured with Maskinporten. Read more about this.

January 4, 2024

Endpoints

/api/enheter
/api/underenheter

Changes

New in version 1

• Add new query parameters
  • "forretningsadresse.kommunenummer". Filter entities on business address only.
  • "beliggenhetsadresse.kommunenummer". Filter sub-entities on location address only.

New in version 2:

• Add new query parameters
  • "forretningsadresse.kommunenummer". Filter entities on business address only.
  • "beliggenhetsadresse.kommunenummer". Filter sub-entities on location address only.
• Chang query parameters
  • kommunenummer
  • Before: Filter entities/sub-entities on business/location addresss
  • Now: Filter entities/sub-entities on municipality number in postal address or business/location addresss.

November 21, 2023

Endpoints

/api/enheter
/api/enheter/{orgnr}
/api/enheter/lastned
/api/enheter/lastned/csv
/api/enheter/lastned/regneark

Changes

New in version 2:

• Add new fields in json, csv, excel and api
  • underAvviklingDato
  • tvangsavvikletPgaManglendeSlettingDato
  • tvangsopplostPgaManglendeDagligLederDato
  • tvangsopplostPgaManglendeRevisorDato
  • tvangsopplostPgaManglendeRegnskapDato
  • tvangsopplostPgaMangelfulltStyreDato

September 13, 2023

Endpoints

/api/enheter
/api/enheter/{orgnr}
/api/enheter/lastned
/api/enheter/lastned/csv
/api/enheter/lastned/regneark
/api/underenheter
/api/underenheter/{orgnr}
/api/underenheter/lastned
/api/underenheter/lastned/csv
/api/underenheter/lastned/regneark

Changes

Change cells in csv files to contain full values for:

• postadresse, forretningsadresse and frivilligMvaRegistrertBeskrivelser for entities
• postadresse, beliggenhetsadresse and frivilligMvaRegistrertBeskrivelser for sub-entities

Introduced in version 2:

• Change query parameters "fraAntallAnsatte" and "tilAntallAnsatte". It is not possible to search with numbers between 1-4. You will now get a 400 response.
• Change response field antallAnsatte. The field is no longer mandatory and will be null when the business has between 0-4 employees.
• Add new response fields
  • harRegistrertAntallAnsatte. The field has been introduced to compensate for the change in the number of employees.
  • hjelpeenhetskode
  • hjelpeenhetskode.kode
  • hjelpeenhetskode.beskrivelse
• Remove response fields
  • naeringskode1.hjelpeenhetskode
  • naeringskode2.hjelpeenhetskode
  • naeringskode3.hjelpeenhetskode
• Put quotation marks around file names in the content-disposition header for all file downloads.

Introduced in version 2 for entities:

• Add new fields to JSON, CSV, Excel, and API.
  • konkursdato
  • vedtektsdato
  • vedtektsfestetFormaal
  • aktivitet

July 27, 2023

Endpoints

/api/enheter/lastned/csv
/api/underenheter/lastned/csv

Changes

Introduce total inventory in CSV format

We will try, as far as possible, not to break backward compatibility with our users. However, it may be necessary in some situations, for example for legal reasons or maintenance, to make changes that involve such a break.

In this case, we will version the service so that the latest version will be available along with the previous version. If you do not use versioning in the accept header, you will get the latest version.

An older version will be considered outdated/deprecated, and will eventually be removed. If there is a need for this type of change, we will try to give the user ample time, and notify about the change in advance.

When is a new version introduced?

We will introduce a new version when we introduce a change that affects backward compatibility. Minor changes and patches will not result in a version change in the header.

Example of a change that results in versioning:

• Remove or change the name of an attribute in the HTTP response.
• Remove or change the name of a REST endpoint.

When is a version removed?

We will issue warning/operational messages well in advance at https://www.brreg.no/om-oss/driftsmeldinger/. You can also subscribe to an RSS feed (https://www.brreg.no/produkter-og-tjenester/rss-feed/)

How do I choose a version?

You can choose a version by specifying the HTTP Accept-header. Use the header specified in this table.

If you do not specify an Accept-header, you will automatically get the latest version after March 11, 2024.

It is possible in most endpoints to browse the result set via page+size, but with certain limitations. (Page+1)*size cannot exceed 10,000. When querying more than 10,000, the service will return HTTP status 400 with an accompanying error message.

If the purpose of browsing deeply into the service is to retrieve all entities, one can instead use the download services. See the chapter on maintaining a copy. These are updated once a day. To update the entities, one can use the update service, and further make individual queries on the entities that have received a change.

To maintain a copy of the CCR, here is the process we have set up:

• Download total inventory for entities

• Download total inventory for sub-entities

• Download total inventory for roles

PS! Files are produced every night, around 05:00 AM.

• You can, for example, store or index a selection of objects in your own database.

PS! The total inventory files are large and may not fit in memory all at once. We recommend using a streaming function to read the file little by little.

• Fetch updates for entities

• Fetch updates for sub-entities

• Fetch updates for roles

PS! You can start your copying job from an early ID or a time well before the total inventory is produced. This ensures that you capture all changes!

If there have been new updates since the last time you updated, retrieve the entire object again:

• Fetch entities

• Fetch sub-entities

• Fetch roles

Retrieving roles with a personal identification number is protected by authentication against Maskinporten.

To use this API, you must have a client in Maskinporten with one of these two scopes:

1. brreg:data:enhetsregisteret
2. brreg:data:enhetsregisteret:auto

If you are a public sector entity (STAT, KOMM, FYLK, ORGL, and ADOS), you have already been assigned the scope brreg:data:enhetsregisteret:auto.

Everyone else must apply for access by sending an email to opendata@brreg.no and will be assigned the scope brreg:data:enhetsregisteret if we approve the access.

Remember that even if you have been granted the right to use one of the scopes, you must also add the scope to your own client in Maskinporten.

Read here how to authenticate with Maskinporten.

Calls to the API for retrieving roles with a personal identification number require sending a JWT signed by one of the two authentication methods described in the link above. You must also set the resource claim in the JWT grant to https://data.brreg.no/enhetsregisteret/autorisert-api before signing it and sending it to https://maskinporten.no. In the pre production environment, this must be set to https://data.ppe.brreg.no/enhetsregisteret/autorisert-api. When using the pre production environment, you must use https://test.maskinporten.no to retrieve the token. The Bearer token must be a JWT signed by either an enterprise certificate or an asymmetric key.

Example query in curl:

curl -v -X GET -H "Authorization: Bearer $SIGNED_JWT_TOKEN" \
    https://data.brreg.no/enhetsregisteret/autorisert-api/enheter/123456789/roller

Click here for more information about the endpoint.

Generic endpoints

Operations against the CCR for entities

Operations against the CCR for sub-entities

Operations against the CCR for roles