LastLoad vs. LastUpdated

This page is relevant when using the various delta endpoints, such as for companies, people and production units.

The CVR registry has two main dates to use when searching for changes: LastLoad and LastUpdated.

LastUpdated is when a company change is registered, i.e. the date and time of an address change. LastLoad is when the company change is made public on CVR's website and APIs.

This is an important distinction, as there might be a delay between a change registration and the publication of it. The publication often happens right after the registration, but in some cases there is a delay.

This delay can cause you to miss some changes, if relying only on LastUpdated to filter the records, as they might not have been publicized yet. For instance, if you at 12:00 AM ask for the changes of the previous day, you risk that changes made at 11:59 PM have not been made public yet, and therefore will not be inlcuded in the result.

Therefore we recommend always using LastLoad to filter the results. This is done by adding the parameter useLastLoad=true to your query. When doing so, LastLoad will be used as a filter with your since parameter as value.

The downside of this approach is that CVR can re-publicize data without any real change, which may return irrelevant results when using LastLoad. To reduce this, we combine LastLoad with LastUpdated: an entity is only returned if it was updated within maxDaysSinceUpdate days before your since date.

maxDaysSinceUpdate defaults to 7 days, which is usually enough to catch any delayed updates.

We recommend using LastLoad

While the default is LastUpdated, we recommend you switch to LastLoad to avoid missing updates. This will later be the default behaviour

NOTE: useLastLoad is not relevant for reports.