> ## Documentation Index > Fetch the complete documentation index at: https://docs.privy.io/llms.txt > Use this file to discover all available pages before exploring further. # Intent webhooks Privy emits webhooks when the status of an intent changes, enabling your application to react to approval events in real time. Use these webhooks to notify reviewers, trigger automations, or keep external systems in sync with the approval flow. Webhooks can be tested at no cost in development environments. To enable webhooks in production, upgrade to the Enterprise plan in the Privy Dashboard. ## Setup Follow the [webhooks setup guide](/api-reference/webhooks/overview#registering-an-endpoint) to register an endpoint, then enable the intent events your app needs. Privy will emit a signed webhook to your endpoint whenever the status of an intent changes, and will retry delivery if the endpoint does not successfully respond. See the [webhooks reference](/api-reference/webhooks/overview#webhook-delivery) for details on delivery, idempotency, and retries. ## Events ### `intent.created` Fired when an intent is proposed, either via the Privy Dashboard or the REST API. The payload includes the list of **authorizers** eligible to approve the request and an `expires_at` timestamp indicating when the intent will expire if the required approvals are not satisfied. Use this event to notify reviewers that a new intent is awaiting their approval. List of key quorums assigned to the intent. Name of the key quorum. Number of approvals required from this quorum. Members of the quorum. The member type (e.g., `'user'`). The Privy DID of the member. Email address of the member. Timestamp of when this member signed. Null if they have yet to sign. UNIX timestamp after which the intent expires and can no longer be executed. Intents expire 72 hours after creation by default. Build alerting around the `expires_at` field to remind reviewers before the window closes. View the complete `intent.created` webhook payload. ### `intent.authorized` Fired when a team member approves an intent. This event indicates that one reviewer has submitted their authorization. *It does not guarantee the intent has been executed.* If the approval meets the authorization threshold, the intent executes automatically. If more approvals are still required, the intent remains in the **Pending** state until the threshold is reached or the intent expires. Use this event to track approval progress or trigger follow-up actions once a specific reviewer has signed off. The team member who authorized the intent. The member type (e.g., `'user'`). The Privy DID of the member. Email address of the member. Timestamp of when this member signed. UNIX timestamp when the team member signed the intent. View the complete `intent.authorized` webhook payload. ### `intent.rejected` Fired when an intent is rejected. A rejected intent is in a terminal state and cannot be approved or executed. Use this event to notify the intent proposer that their request was denied, or to trigger cleanup logic in external systems. UNIX timestamp when the intent was rejected. A rejected intent is in a terminal state. To retry the action, propose a new intent with the same parameters. View the complete `intent.rejected` webhook payload. ### `intent.executed` Fired when an intent has been fully approved and the proposed action executes successfully. For example, a transaction was sent and broadcasted. Use this event to confirm that the action is complete and to retrieve execution results such as a transaction hash. Result of the failed intent execution. HTTP status code from the action execution. UNIX timestamp when the action was executed. Display name of the key quorum that authorized execution. ID of the key quorum that authorized execution. Response from the execution. For transaction intents, this contains the transaction hash. View the complete `intent.executed` webhook payload. ### `intent.failed` Fired when an intent has been fully approved but the proposed action fails during execution. Common causes include insufficient gas or balance, a policy blocking the transaction, or an on-chain revert. A failed intent is in a terminal state. To retry the action, propose a new intent with the same parameters. Result of the failed intent execution. HTTP status code from the action execution. UNIX timestamp when the action was executed. Display name of the key quorum that authorized execution. ID of the key quorum that authorized execution. Response from the execution, if available. View the complete `intent.failed` webhook payload.