Consume executed actions

Once a sufficient threshold of users have approved an intent, Privy will automatically execute the intent. Organizations can then retrieve the result of the executed intent (e.g. a signature or a transaction hash) or a failure reason if there was an error. Organizations may either fetch intents by ID or subscribe to webhooks to consume the result of intent execution.

Fetch intent by ID

Organizations can fetch intents by ID using Privy’s GET /v1/intents/:id endpoint. The returned intent will include its status, creator, the users that approved the intent, the execution result and more.

Intent webhooks

Your application may also subscribe to intent webhooks to consume the result of intent execution. Your application can forward these webhooks as notifications to the organizations you serve, to notify them of newly created intents, new approvals, and intent execution. Follow this guide to subscribe to Privy’s webhooks and enable webhooks for the following any of the following events.

Event	Description
`intent.created`	A new intent was created. Can be used to notify organizations and users of a new pending intent.
`intent.authorized`	An intent has received sufficient authorization signatures to meet the threshold, but has not yet been executed yet.
`intent.executed`	An intent has been executed successfully after receiving sufficient authorization signatures.
`intent.failed`	An intent encountered an error during execution after receiving sufficient authorization signatures.
`intent.rejected`	A user of the organization rejected the intent before it received sufficient authorization signatures.

Organizations

Setup

Taking actions

Approving actions

Conditional policies

Consume executed actions

Fetch intent by ID

Intent webhooks

​Fetch intent by ID

​Intent webhooks

Fetch intent by ID

Intent webhooks