POST
/
api
/
v1
/
smart-accounts
/
{smart_account_address}
/
spending-limits
/
{spending_limit_address}
/
transactions
Create a debit against a spending limit
curl --request POST \
  --url https://developer-api.squads.so/api/v1/smart-accounts/{smart_account_address}/spending-limits/{spending_limit_address}/transactions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-squads-network: <x-squads-network>' \
  --data '{
  "amount": "<string>",
  "signer_address": "<string>",
  "recipient_address": "<string>",
  "fee_config": {
    "currency": "<string>",
    "payer_address": "<string>"
  }
}'
{
  "transaction": "<string>",
  "fee": {
    "amount": "<string>",
    "amount_decimal": "<string>",
    "currency": "<string>",
    "sol_equivalent": {
      "amount": "<string>",
      "amount_decimal": "<string>"
    }
  }
}

Use a spending limit to move tokens between addresses.

​
Key Concepts

  • Spending Limit Validation: The amount must be within the remaining limit
  • Transaction Signing: Only authorized signers can create transactions
  • Destination: Tokens will be sent to the specified destination address

​
Important Notes

  • The amount cannot exceed the remaining limit
  • The spending limit must not be expired
  • The destination must be an allowed address if the spending limit has destination restrictions

Authorizations

​
Authorization
string
header
required

UUID-based API key provided by Squads

Headers

​
x-squads-network
enum<string>
required

Specifies the network for the API request

Available options:
mainnet,
devnet

Path Parameters

​
smart_account_address
string
required

The address of the smart account

​
spending_limit_address
string
required

The address of the spending limit

Body

application/json

Response

200
application/json

Debit created successfully

The response is of type object.