> For the complete documentation index, see [llms.txt](https://docs.ironblocks.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ironblocks.com/platform/threat-detection/api-and-web-hook/webhook.md).

# Webhook

Register your own webhook to receive live notificationsYou can register your own webhook to be notified (`POST`) in real-time on any suspicious or critical transactions targeting your protocol.Ironblocks support team will contact and help you to set it up. Following is an example of the different types of variables that can be sent in the notification:

### Post body example <a href="#post-body-example" id="post-body-example"></a>

`POST` `https://your-domainl/your-path`

**Request Body**

| Name                | Type      | Description                                                                         |
| ------------------- | --------- | ----------------------------------------------------------------------------------- |
| protocol            | string    | The name of your protocol.                                                          |
| chainId             | integer   | The id of the underlying blockchain                                                 |
| assets              | \[string] | A list of protocol addresses that were present in the transaction.                  |
| transferredUSD      | integer   | The amount transferred (in/out) the protocol, as a signed int.                      |
| txHash              | string    | The transaction hash string.                                                        |
| severity            | enum      | The inspection status: `critical`, `suspicious`                                     |
| watch\_event\_codes | \[enum]   | Any the following: `anchor_z`, `asymmetric_balance`, `malicious_admin`, `open_door` |

You can ask to add/subtract variables to match your protocol Database.