Create an intent to update a key quorum. The intent must be authorized by the key quorum members 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 key quorum.
Request input for creating or updating a key quorum.
List of P-256 public keys of the keys that should be authorized to sign on the key quorum, in base64-encoded DER format.
The number of keys that must sign for an action to be valid. Must be less than or equal to total number of key quorum members.
x >= 150List of user IDs of the users that should be authorized to sign on the key quorum.
List of key quorum IDs that should be members of this key quorum. Key quorums can only be nested 1 level deep.
1 - 5 elementsCreated key quorum update intent.
Response for a key quorum 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
KEY_QUORUM The original key quorum update request that would be sent to the key quorum endpoint
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 key quorum before any changes. If undefined, the resource was deleted and no longer exists
Result of key quorum update execution (only present if status is 'executed' or 'failed')