Report publications
We recommend using our monitoring service instead
While polling the data might be required for some cases, constantly asking for changes has a huge overhead. With our monitoring services, you can get real-time updates when changes occur, pushed directly to you. For more information, see our Monitoring documentation
Sometimes it is necessary to know which reports have changed since a specific date, for instance if you have a service that continuously updates your database with the newest reports from CVR.
Endpoint
When scrolling through reports, you can either ask for the full report, or just for the metadata.
GET api.lassox.com/data/cvr/reports/delta?since=2021-02-01&max=2021-02-10&pageSize=50
You can include the parameter 'metadataOnly=true' to receive only the metadata-fields of the report. See the Key figures page for details on metadata.
The query parameters since, max, pageSize and cToken work as described for the entity delta endpoints. Note that useLastLoad is not relevant for reports.
Response
Regardless of which data you request, you will receive a scrolled result, including a continuationToken, an indicator of whether or not there is a next page, and variouts counts. Scrolled indicates that you can scroll to the next page, but cannot scroll back, due to limitations in the CVR registry.
{
"continuationToken": STRING,
"hasNextPage": true,
"totalPages": 32,
"results": [
... list of requested entities here ...
],
"page": 1,
"pageSize": 100,
"resultsFound": 3200,
"resultsReturned": 100
}
If there are more results than can fit in a single request, you will be given a ContinuationToken that can be provided with the queryparameter cToken to retrieve the next page. Unfortunately, we are limited by the CVR registry in this regard, and the ContinuationToken will only be valid for 3 minutes, so ensure your pageSize is small enough that you can handle the results in under that time. Also note that repeated requests with the same cToken will continue the paging, but will not increment the page number. This is due to limitations in the CVR registry, and we advise to always use the returned continuationToken, and only once.