# 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:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Base Employee webhooks</td><td><a href="../../employee-api/base-employee-api/endpoints/webhook-subscriptions">webhook-subscriptions</a></td></tr><tr><td>Clean Employee webhooks</td><td><a href="../../employee-api/clean-employee-api/endpoints/webhook-subscriptions">webhook-subscriptions</a></td></tr><tr><td>Multi-source Employee webhooks</td><td><a href="../../employee-api/multi-source-employee-api/webhook-subscriptions">webhook-subscriptions</a></td></tr></tbody></table>

## 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           |

{% hint style="info" %}
**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.
  {% endhint %}

### 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.

{% code title="Example payload" %}

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

{% endcode %}

### Status for Experience changes

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

### 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.coresignal.com/api-introduction/webhooks/experience-webhooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.