> For the complete documentation index, see [llms.txt](https://www.docpartner.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.docpartner.dev/en/api/mail-partner/webhooks.md).

# Webhooks

Manage the statuses of your email campaigns

After sending a campaign, Mail Partner lets you receive statuses via webhooks.\
For more information, [**contact us**](https://www.mailpartner.fr/contact).

{% hint style="info" %}

#### Please note

To receive statuses, you must set your webhook URLs

in your [Mail API](https://my.mailpartner.fr/dashboard/webhooks/liste) tab
{% endhint %}

**The possible statuses are:**

* **Delivered:** The email was accepted by the recipient's mail server. This indicates a successful delivery.
* **Hard-Bounce:** Permanent and definitive delivery failure. This means the email address does not exist, is misspelled, or the domain is invalid. The address should be removed from your list.
* **Soft-Bounce:** Temporary delivery failure. Reasons may include a full inbox, a temporarily down server, or a message that is too large. A new send attempt can be made later.
* **Open:** Indicates that the recipient opened the email, generally measured by the loading of an invisible pixel. This suggests engagement and the effectiveness of the subject line and preview.
* **Click:** Means the recipient clicked on one or more links within the email. This reflects high engagement and interest in the email's content.
* **Unsubscribe:** The recipient clicked on the unsubscribe link, indicating they no longer wish to receive emails. It is crucial to process this request immediately by removing the address from your sending list.
* **Spam:** The email was marked as spam or blocked by a spam filter. This seriously harms your sender reputation and requires treating the address as a forced unsubscribe.

**Example of a JSON status sent via POST**

```json
{
  "hook": "open",
  "datas": {
    "op": "open",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}
```

```json
{
  "hook": "open",
  "datas": {
    "op": "first_open",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}  


```

```json
{
  "hook": "delivered",
  "datas": {
    "op": "delivered",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}
```

```json
{
  "hook": "click",
  "datas": {
    "op": "click",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}
```

```json
{
  "hook": "hard-bounce",
  "datas": {
    "op": "hard-bounce",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}
```

```json
{
  "hook": "soft-bounce",
  "datas": {
    "op": "soft-bounce",
    "at": 1764770972,
    "from": "myemail@email.com",
    "message_id": "xxxxxx"
  }
}
```

##


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.docpartner.dev/en/api/mail-partner/webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.