Who sits on the board?
The registered roles at a company: Chair of the Board, managing director, auditor and the rest, each with who holds the role and since when.
Nøkkelen virker i dag på Leietaker-API og dagens Data API; Placepoint API godtar samme nøkkel når det lanseres.
Prøv med et ekte company: Eksempel Eiendom AS
- Trial key with GitHub in under a minute
- One GET call
- ISO 6523 identifiers
- Norway and Sweden
- Verified against Brønnøysundregistrene
ℹ️ The endpoint responds once the Placepoint API has launched. The contract below is final; the Tenant API already responds.
From organisation number to role list
The call answers who actually runs the company. Credit assessors use the role list to see who has signing authority before an agreement is made, agents use it to identify the right contact person at the counterparty, and compliance teams use it to check whether a person recurs across several companies.
Each role has a holder: a person or another company. A company that holds a role, for example as auditor, comes with a full organisation number and name. A person comes with a year of birth by default; the full name also requires the owners.read scope, the same restriction that the owner lookup on a property uses.
sinceDate states when the role started, so you can see whether a change on the board is recent or has stood unchanged for years.
One call for the whole board
All roles at the company come in a single list: Chair of the Board, managing director, auditor and the rest, instead of looking them up one by one in a manual register search.Company and person in the same schema
An auditor that is a company and a managing director who is a person come in the same field structure, withholder.kindtelling them apart. No separate branch to parse for each type.Since when, not just who
sinceDateshows how long a role has stood. A recent change on the board is a signal in itself, not just who sits there today.
Fields that actually say something
One GET call on the company's scheme and id gives you the whole role list. The fields below are the ones that decide what you can read out of each role.
/companies/{scheme}/{id}/rolescurl -X GET "https://data.placepoint.no/companies/0192/987654321/roles" \
-H "Authorization: Bearer $TOKEN"
svar · 200
{
"items": [
{
"role": "CHAIR",
"holder": {
"kind": "PERSON",
"person": {
"birthYear": 1975
}
},
"sinceDate": "2019-06-01"
},
{
"role": "CEO",
"holder": {
"kind": "PERSON",
"person": {
"birthYear": 1980
}
},
"sinceDate": "2021-01-15"
},
{
"role": "AUDITOR",
"holder": {
"kind": "ORGANIZATION",
"organization": {
"organizationIdentifier": {
"scheme": "0192",
"id": "912345678"
},
"name": "Revisor AS",
"country": "NO"
}
},
"sinceDate": "2020-03-01"
}
]
}
holder.kind states whether person or organization is filled in. Without the owners.read scope, only person.birthYear is returned, never the name.
Three steps to your first response
Log in with GitHub
One click, under a minute, no payment card. The key comes back to this page.Call the endpoint
Replace$TOKENin the curl above with your key. The call only needs the scheme and the organisation number you already have from the company lookup.Use the response
Filter onroleto find the Chair of the Board or the managing director directly, or list all the roles for a full overview of who runs the company.
Data and sources
Norwegian roles come from Brønnøysundregistrene's Enhetsregisteret (the Central Coordinating Register for Legal Entities), updated continuously. Swedish roles are verified against Bolagsverket's register via Combify.
See also
Questions and answers
Why do I only get a year of birth and not the person's name?
owners.read scope in addition to companies.read. Without it, the call returns the year of birth where known, the same restriction used on the owner lookup for a property.How fresh is the data?
Does it work in Sweden?
0007 and the Swedish organisationsnummer, and the call responds with the same field set, verified against Bolagsverket's register via Combify.Which role types exist?
role carries the role type itself.