Key Concepts
- Signers and Permissions: Each signer must have specific permissions (CAN_INITIATE, CAN_VOTE, CAN_EXECUTE)
- Threshold: The minimum number of required signatures for any action
- Optional Settings: Configure an admin address to limit the ability to update the account’s settings to only the admin address
Idempotency
You can optionally provide an idempotency key via thex-idempotency-key
header to prevent duplicate account creation. The idempotency key can be any random string and helps ensure that retrying the same request won’t create multiple accounts.
When using idempotency:
- If an account was already created with the provided key → Returns status “created” and the existing account address
- If a request is still being processed → Returns status “pending” and an empty address
- If no idempotency key is provided → Creates a new account and returns status “created” with the new address
Important Notes
- At least one signer must have CAN_INITIATE permission
- The threshold cannot exceed the number of signers with CAN_VOTE permission
- Use idempotency keys when retrying failed requests to prevent duplicate accounts
- The response status field indicates whether the account is ready to use
- Updating an account with an admin_address set requires admin mode
Authorizations
UUID-based API key provided by Squads
Headers
Specifies the network for the API request
Available options:
mainnet
, devnet
Optional idempotency key to prevent duplicate account creation. If provided, the API will return the same result for identical requests.
Body
application/json
Response
Smart account creation request processed successfully