Skip to main content
POST
Create Transaction

Authorizations

X-API-KEY
string
header
required

API key required for authentication

Headers

x-idempotency-key
string

Unique string, such as a UUID, that identifies this request. It is not the transaction ID. To retry the request, send it again with the same key. If a transaction already exists for this key in the project, the API returns that transaction in its current status and ignores the new request body. Keys do not expire and are not returned in responses. See Transfer Tokens for details.

Path Parameters

walletLocator
string
required

A wallet locator can be of the format:

  • <walletAddress>
  • email:<email>:<chainType>[:<walletType>][:alias:<alias>] (walletType defaults to 'smart')
  • userId:<userId>:<chainType>[:<walletType>][:alias:<alias>] (white label user example)
  • phoneNumber:<phoneNumber>:<chainType>[:<walletType>][:alias:<alias>]
  • twitter:<handle>:<chainType>[:<walletType>][:alias:<alias>]
  • x:<handle>:<chainType>[:<walletType>][:alias:<alias>]
  • me:<chainType>[:<walletType>][:alias:<alias>] (Use when calling from the client side with a client API key)
  • chainType[:<walletType>]:alias:<alias>

Body

application/json

Input schema for creating a new transaction. The parameters vary based on the wallet type (EVM vs Solana vs Stellar).

params
object
required
fees
object

Optional per-transaction fee configuration override. When omitted, the project default is used.

Response

The transaction has been successfully created.

Complete transaction response including status, signing requirements, and wallet type specific data

chainType
enum<string>
required

The blockchain type of the wallet

Available options:
aptos,
evm,
solana,
stellar,
sui
createdAt
required

ISO timestamp when the transaction was created

id
string
required

Unique identifier for the transaction

onChain
EVM MPC wallet transaction data · object
required

Transaction data specific to EVM MPC wallets

params
object
required
status
enum<string>
required

Current status of the transaction

Available options:
awaiting-approval,
failed,
pending,
success
walletType
enum<string>
required

The wallet type (smart or mpc)

Available options:
mpc,
smart
approvals
object

Complete approval data including requirements, pending and submitted signatures

completedAt

ISO timestamp when the transaction reached finality

error
object

Error message if the transaction fails after submission

fees
object

Transaction fee information including actual transaction fees, billed amounts, and billing status

sendParams
object