Responses, errors and quota
Response format
A successful call answers with status and data:
{ "status": "success", "data": { } }An error has the HTTP status of the error and this body:
{ "status": "error", "error": { "code": 403, "message": "insufficient_scope: this endpoint requires the scope 'properties'" } }Add ?pretty=1 to a call to pretty-print the answer.
Your plan decides what you see
The scope decides whether you can call an endpoint. Your ownr plan (Gratis, All insights or Premium) decides how much of the answer you get.
- Fields your plan does not include are
null, and the object that holds them lists their names inrestricted, e.g."restricted": ["tinglysning", "access_holders"]. Anullfield not listed there is genuinely empty. - Fields and filters that need Premium are marked (Premium) in the reference.
- Segment filters your plan does not include are ignored, so
countreflects only the filters your plan covers. If every filter is ignored, the answer is400 No filters supplied. - Beneficial owners also require
beneficial_purposeandbeneficial_accept=1. See Purposes allowed for beneficial owners lookup.
The plan can change without a new token: after an upgrade or downgrade, the next call returns the new set of fields.
Error codes
| Status | Meaning |
|---|---|
400 |
Invalid input, e.g. an unknown parameter on a segment endpoint, or a search query shorter than 3 characters |
401 |
Missing, invalid or expired access token |
402 |
Payment or capacity needed: an unpaid segment, no lead capacity, or Ajour without a licence or a purchased Ajour. The body links to where to buy |
403 |
The token does not have the scope the endpoint needs |
404 |
Not found. Data that belongs to another company is also 404 |
409 |
Conflict, e.g. the item is already in the list |
429 |
The quota or the hourly limit is reached |
A 429 answer has a Retry-After header (seconds) and says in error.message whether the quota or the hourly limit was hit. If it was the quota, error.upgrade_url links to where you change API tier.
Lists and paging
Paged answers have items, count, page, pageCount, nextPageUrl and prevPageUrl. Use page to move through them.
- Search (
/…/search) is for finding one specific entity, not for exporting lists.qtakes 3 to 100 characters,limit1 to 10 results per page, and a search has at most 10 pages. - Filter lookups (
/…/segments) return the totalcountand up to 3 example items. - Full lists come from a purchased segment: buy it in ownr, then read it with
GET /segments/downloads/{id}, 20 rows per page. See the segments guide.
IDs and references
| Entity | ID |
|---|---|
| Company | CVR number |
| Production unit | P number |
| Person | ownr person id |
| Property | DAF id (string) |
| Annual report | Report id |
Every reference to another entity uses the same item object: {"id", "slug", "url", "name"}. url is the API path to fetch it.
Quota and limits
Your organisation has one quota, shared by all its keys.
- Free: 1,000 calls a month, counted from the day API access was activated.
- Purchased API tier: from 5,000 to 1,000,000 calls a month. The quota resets monthly on the billing day, also when it is paid yearly. An administrator buys or changes the tier under API Adgang, and an upgrade applies at once. See prices.
| Calls | |
|---|---|
| Counted | Successful (2xx) calls to data endpoints: /company, /p-unit, /report, /person, /property, segment filter lookups and /beneficial-owners/purposes. MCP calls to these endpoints count the same way |
| Not counted | Errors (4xx, 5xx, 429), /token, /pipelines…, follow, Ajour, /account/…, /segments/downloads… and webhook deliveries |
When the quota is used up, the counted endpoints answer 429 until it resets. The others keep working. The organisation’s administrators get an e-mail at 80% and 100% of the quota.
There is also an hourly limit, which every call counts towards: 300 calls an hour on the free tier and 1,000 to 60,000 on the purchased tiers. There is no limit per second.
Headers
| Header | Content |
|---|---|
X-Quota-Limit |
Calls in the current quota period |
X-Quota-Remaining |
Calls left in the quota period |
X-Quota-Reset |
When the quota resets (ISO 8601) |
X-RateLimit-Limit |
Calls allowed in the current hour |
X-RateLimit-Remaining |
Calls left in the current hour |
X-RateLimit-Reset |
Seconds until the hourly limit resets |
The quota headers are sent by the endpoints that count against the quota. The hourly headers are on every answer.
How fresh is the data?
ownr imports data from the public registers (CVR, BBR, Tinglysning, Statstidende and annual reports) in batches. Answers are as fresh as the latest import, not real time.