Experience Webhooks

The Experience Webhooks deliver weekly notifications when employees start new positions, get promotions, or close existing ones. These structured updates help you monitor meaningful career changes across companies and industries without the need for constant manual checks or API calls.

Find endpoints and subscription examples in the corresponding topics:

Base Employee webhooks

Clean Employee webhooks

Multi-source Employee webhooks

Subscription frequency

Delivery frequency is determined by the specific API data source you are utilizing. Corresponding cadence:

API source	Update frequency
Base Employee API	Daily
Clean Employee API	Weekly
Multi-Source Employee API	Weekly

Multi-source, Clean, or Base?

• Multi-source datasets contain cleaned and enriched data combining information from multiple sources.

• Clean datasets are derived from our Base data and cleaned to ensure the best quality.

• Base datasets freshly scraped and structured/updated for easier use.

Webhook payload

Each webhook notification includes the following fields:

• member_id – The ID of the employee profile that was updated.

• status – Notifies a changed state.

Example payload

[
  {
    "member_id": 125,
    "status": "changed"
  }
]

Status for Experience changes

Status	Description
changed	Profiles that have undergone non-specified changes in the experience section. To see the exact changes, you will need to query them using Bulk Collect GET or collection endpoints.

Webhook triggers

The subscribed experience change webhook is triggered when:

1. Employee starts a new experience position

2. Employee closes their previously open experience position