Headers
API key required for authentication
Unique key to prevent duplicate transaction creation
Path Parameters
A wallet locator can be of the format:
<walletAddress>
email:<email>:<chainType>[:<walletType>]
(walletType defaults to 'smart')userId:<userId>:<chainType>[:<walletType>]
(white label user example)phoneNumber:<phoneNumber>:<chainType>[:<walletType>]
twitter:<handle>:<chainType>[:<walletType>]
x:<handle>:<chainType>[:<walletType>]
me:<chainType>[:<walletType>]
(Use when calling from the client side with a client API key)
Body
Input schema for creating a new transaction. The parameters vary based on the wallet type (EVM vs Solana vs Stellar). Parameters for a transaction from a Solana Smart Wallet
Response
The transaction has been successfully created.
Complete transaction response including status, signing requirements, and wallet type specific data
The blockchain type of the wallet
evm
, solana
, aptos
, sui
, stellar
The wallet type (smart or mpc)
smart
, mpc
Transaction data specific to EVM smart wallets
Unique identifier for the transaction
Current status of the transaction
awaiting-approval
, pending
, failed
, success
ISO timestamp when the transaction was created ISO 8601 formatted timestamp
"2024-01-01T00:00:00.000Z"
Complete approval data including requirements, pending and submitted signatures
ISO timestamp when the transaction reached finality ISO 8601 formatted timestamp
"2024-01-01T00:00:00.000Z"
Error message if the transaction fails after submission