> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/SaaS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/SaaS/request/notifications/reference-guides/webhooks.md).

# Webhooks

Webhooks provide an automated way to receive real-time notifications about key actions and events within the Request app. You can integrate webhooks with the services you use daily, like [Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet), PagerDuty, etc. The following webhook types are sent out:

| Webhook type                                                    | Description of event that kicks off the webhook           |
| --------------------------------------------------------------- | --------------------------------------------------------- |
| `marketplace.data_product.access_requests.consumer.updated`     | A determination is made on an access request              |
| `marketplace.data_product.access_requests.created`              | A consumer requests access to a data product              |
| `marketplace.data_product.access_requests.deleted`              | The data product you have an access request to is deleted |
| `marketplace.data_product.access_requests.expired`              | A consumer's access to a data product expires             |
| `marketplace.data_product.access_requests.expiring`             | A consumer's access to a data product will expire soon    |
| `marketplace.data_product.access_requests.revoked`              | A consumer's access to a data product is revoked          |
| `marketplace.data_product.access_requests.canceled`             | An access request to a data product is canceled           |
| `marketplace.data_product.state.created`                        | A data product is published                               |
| `marketplace.data_product.state.deleted`                        | A data product is deleted                                 |
| `marketplace.data_product.data_sources.updated`                 | A data product's data sources are updated                 |
| `marketplace.data_product.access_requests.data_steward.updated` | A data product's data stewards are updated                |
| `marketplace.data_product.access_requests.pending`              | A reminder for pending access requests                    |

<details>

<summary>Example of a <code>marketplace.data_product.data_sources.updated</code> event webhook</summary>

```
{
  "timestamp": "2025-07-22T18:16:14.608998951Z",
  "data": {
    "actionLink": "https://app.immutacloud.com/marketplace/data-product/{Id}/data-sources?accountId={accountId}",
    "dataProductId": "12345",
    "dataProductName": "US East Customers"
  },
  "type": "marketplace.data_product.data_sources.updated"
}
```

</details>

## Webhook history

To ensure your webhook is set up and working correctly, you can view the status of the notification delivery attempts for your webhooks. To do this, select the webhook from the settings and open the **History** tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://documentation.immuta.com/SaaS/request/notifications/reference-guides/webhooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.