Webhook payload

The data sent by the CVR event webhook will tell you the who, the when and the what about the CVR update. Whenever possible, we also provide the data prior to the event, meaning that you can make comparisons that might suit your business needs. If you need to know if the employee count change caused a rise or decline in employees, this can easily be answered through the data provided by the webhook.

Below is an example of the webhook payload that is sent when a company changes status and a person leaves management.

{
    "lassoId":"CVR-1-34580821",
    "timestamp" : "2018-09-15T09:50:30.890Z",
    "updates": {
        "status": {
            "updated": true, 
            "before": "NORMAL", 
            "after": "UNDER KONKURS" 
        },     
        "name": { 
            "updated": false, 
            "before": null, 
            "after": null,
        },
        "management": { 
            "updated": true, 
            "added": [], 
            "removed": [
                { 
                    "name": "Jens Jensen", 
                    "lassoId": "CVR-3-8172635419",
                    "type": "Person"
                }
            ] 
        }
        ... other events exluded for brevity ...
    }
}

• lassoId is the company related to event. Read about Lasso Ids.
• timestamp is the time that the event was registrered in CVR.
• updates is an object containing all the potential changes made. Please note that all update types are sent, but it's the updated field in each update that tells you if a particular type of change was made. Data will therefore not be available if this is false. For the sake of brevity, we've left out most event types above. See below for a complete list.