Create an intent to add a rule to a policy. The intent must be authorized by the policy owner before it can be executed.
Basic Auth header with your app ID as the username and your app secret as the password.
ID of your Privy app.
ID of the policy.
The rules that apply to each method the policy covers.
1 - 50Method the rule applies to.
eth_sendTransaction, eth_signTransaction, eth_signUserOperation, eth_signTypedData_v4, eth_sign7702Authorization, signTransaction, signAndSendTransaction, exportPrivateKey, signTransactionBytes, * The verbatim Ethereum transaction object in an eth_signTransaction or eth_sendTransaction request.
Action to take if the conditions are true.
ALLOW, DENY Created rule intent.
Response for a rule intent
Unique ID for the intent
Display name of the user who created the intent
Unix timestamp when the intent was created
ID of the resource being modified (wallet_id, policy_id, etc)
Detailed authorization information including key quorum members, thresholds, and signature status
Current status of the intent
pending, executed, failed, expired, rejected, dismissed Unix timestamp when the intent expires
RULE The original rule request. Method is POST (create), PATCH (update), or DELETE (delete)
ID of the user who created the intent. If undefined, the intent was created using the app secret
Unix timestamp when the intent was rejected, present when status is 'rejected'
Unix timestamp when the intent was dismissed, present when status is 'dismissed'
Human-readable reason for dismissal, present when status is 'dismissed'
Current state of the rule before any changes. Undefined for create intents or if the rule was deleted
Parent policy containing this rule, including sibling rules for contextual display
Result of rule execution (only present if status is 'executed' or 'failed')