> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.flagright.com/framl-api/guides/webhooks/introduction/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.flagright.com/_mcp/server.

A webhook enables Flagright to push real-time notifications to your app. Flagright uses HTTPS to send these notifications to your app as a JSON payload. You can then use these notifications to execute actions in your backend systems.

Webhooks are particularly useful when:

* A transaction is investigated and approved by your compliance team.
* A user's state has changed.
* A new case or alert is created.
* A case or alert is closed.
* A rule action has been updated.
* A Suspicious Activity Report (SAR) is created, submitted, or accepted by the regulator, or a message is received from the regulator on a submitted SAR.

## Steps to Receive Webhooks

You can start receiving event notifications in your app by following these steps:

1. Identify the events you want to monitor and the event payloads to parse.
2. Create a webhook endpoint as an HTTP endpoint (URL) on your server.
3. Handle requests from Flagright by parsing each event object and returning 2xx response status codes.
4. Deploy your webhook endpoint so that it is publicly accessible via an HTTPS URL.
5. Register your publicly accessible HTTPS URL in the Flagright console and store the secret signing key (for verifying the payload) in a secure place.

## Types of Events

[Full list of webhook events](/api-reference/webhooks)

## Event Payloads

| PROPERTY         | DETAILS                                                                   |
| ---------------- | ------------------------------------------------------------------------- |
| id               | Unique identifier for the event                                           |
| type             | Event type (e.g., USER\_STATE\_UPDATED).                                  |
| data             | Object containing data associated with the event.                         |
| createdTimestamp | Time at which the event was created. Measured in ms since the Unix epoch. |

## Sample Event Payload

```json
{
  "id": "2fa554d3-1ffa-4361-9af6-5479c2d4847f",
  "type": "USER_STATE_UPDATED",
  "createdTimestamp": 1661522222301,
  "triggeredBy": "MANUAL",
  "data": {
    "userId": "U-1",
    "state": "BLOCKED",
    "reason": "updated manually"
  }
}
```