Track all notable changes to the Squads Smart Account API
Integrate Passkey Flows
/api/v1/passkeys
endpoint to create or authenticate passkeys via a hosted WebAuthn UI.Update Signer Logic
RESTful API Design The v1 API follows standard REST conventions with a clear resource hierarchy:
Admin Control
Idempotency Support
x-idempotency-key
header for account creation to prevent duplicatesImproved Gas Abstraction
payer_address
in the fee_config
USDT
as a payment token. Use usdt
in the fee_config
to pay with USDT.API Path Structure (High Impact) All endpoints now follow RESTful conventions with a clear resource hierarchy.
Examples: Examples of endpoint changes:
/api/v0/smart_account/transaction/create
→ /api/v1/smart-accounts
/api/v0/smart_account/transaction/threshold/update
→ /api/v1/smart-accounts/{address}
/api/v0/smart_account/transaction/spending_limit/create
→ /api/v1/smart-accounts/{address}/spending-limits
Request Body Format (High Impact)
Response Format (Medium Impact)
Before (v0):
After (v1):
Update Request Paths (High Priority)
Convert all endpoints to follow the new RESTful pattern
Use proper HTTP methods (GET, POST, PATCH, DELETE)
Move smart_account_address
and spending_limit_address
to the url path
Example:
Update Error Handling (Medium Priority)
Add Idempotency for Critical Operations (Low Priority)
x-idempotency-key
header for account creationRequest Body Restructuring (High Impact)
All configuration endpoints now expect smart_account_address
at the top level of the request body.
Affected endpoints:
/api/v0/smart_account/transaction/threshold/update
/api/v0/smart_account/transaction/signers/add
/api/v0/smart_account/transaction/signers/remove
/api/v0/smart_account/transaction/spending_limit/create
/api/v0/smart_account/transaction/spending_limit/update
/api/v0/smart_account/transaction/spending_limit/use
Before:
After:
Create Smart Account Response (High Impact)
The /api/v0/smart_account/transaction/create
endpoint now provides a streamlined experience:
Before:
After:
Update Request Bodies (High Priority)
Move smart_account_address
to the top level
Remove all nested metadata structures
Example for updating threshold:
Update Create Smart Account Integration (High Priority) - Remove transaction submission logic - Remove fee handling code - Account is ready to use immediately after creation - Only expect the smart account address in response