Skip to content

Consume events with webhook

Events can be consumed via Webhook. The available events can be found in the Webhook Event documentation.

This guide highlights the use of PERSON_CHANGED.

Before you begin

This guide assumes a working webhook integration. see Working with webhooks It is enough to listen for the Webhook event 'PERSON_CHANGED'.

This guide assumes an active subscription. see Uploading and identifying your consumers The steps in this are written with a subscription to Gedi ME514F2704C7 which changes every day in sandbox.

The provided example values in this guide must be changed with the values of your client. Replace <client_id> with your client id, and <client_secret> with your client secret.

Receiving a Person change

Step 1 - Interpreting the change event

When a person is updated in our system you will receive a webhook delivery on your webhook. The delivery will have type = "PERSON_CHANGED" and might for instance have gedi = "ME514F2704C7"

Step 2 - Authentication

To communicate with the API, you will need an access_token from the Authentication API (POST:https://login.bisnode.com/sandbox/v1/token.oauth2).

Don't forget to change credentials

Don't forget to replace <client_id> with your client id, and <client_secret> with your client secret.

curl -X POST https://login.bisnode.com/sandbox/v1/token.oauth2 \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "grant_type=client_credentials&scope=bci" \
     -u "<client_id>:<client_secret>"

The property access_token from the response should be used for all other API requests in the Authorization header as the Bearer token.

Step 3 - Get the person

Now use GET:/v3/persons/ME514F2704C7 to get the changed person.

curl -X GET https://sandbox-api.bisnode.com/consumer-intelligence/v3/persons/<gedi> \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer <access_token>"

The response will contain the complete updated person.