Skip to main content
POST
Manage Spending Limit

Authorizations

Authorization
string
header
required

Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"

Headers

x-squads-network
enum<string>
default:mainnet

Specifies which Solana network to use. Defaults to 'mainnet' if not provided. Valid values are 'devnet' or 'mainnet'.

Available options:
devnet,
mainnet

Body

application/json
smart_account_address
string
required

The address of the Smart Account

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
spending_limit_address
string
required

The address of the spending limit to modify

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
amount
string<uint64>
required

The new maximum amount in base units that can be spent within the specified period

token_address
string
required

The address of the token mint for which this spending limit applies

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
period
enum<string>
required

Defines the period for spending limits:

  • ONE_TIME: Limit can only be used once
  • DAY: Limit resets daily
  • WEEK: Limit resets weekly
  • MONTH: Limit resets monthly
Available options:
ONE_TIME,
DAY,
WEEK,
MONTH
transaction_signers
string[]
required

List of addresses that will sign this transaction

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
spending_limit_signers
string[]
required

Updated list of signer addresses that are authorized to use this spending limit

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
destinations
string[]
required

Updated list of allowed recipient addresses. If empty, funds can be sent to any address

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
fee_config
object
required

Response

Spending limit successfully updated

transaction
string
required

The transaction encoded in base64

fee
object
required