For the complete documentation index, see llms.txt. This page is also available as Markdown.

Broadcast a signed swap transaction

Broadcast a signed swap transaction

post

Broadcast a signed swap transaction.

The caller is responsible for signing the transaction data returned by /api/v1/trade/quote.

  • Solana: signed_transaction is a base64-encoded serialized VersionedTransaction

  • EVM (Base): signed_transaction is a 0x-prefixed signed transaction hex

The signed transaction is broadcast as-is; the response reports the resulting transaction hash and status.

⚠️ This endpoint always broadcasts. There is no dry-run mode. Every call that passes validation submits the transaction to the network, and a successful transaction is a real executed trade that moves real funds. No request field prevents that.

The transaction is always simulated first, and the broadcast is aborted if that simulation fails — so a transaction that would revert does not reach the network. Simulation passing is not a preview: it is what allows the broadcast to proceed.

Authorizations
apikeystringRequired

API key for authentication

Body
signed_transactionstringRequired

Signed transaction: base64 for Solana, 0x hex for EVM

Example: 0xdeadbeef
chainstring · enumRequired

Chain the transaction is for: 'solana' or 'base'

Example: basePossible values:
request_idany ofOptional

Jupiter request ID (Solana only)

stringOptional
Responses
200

Execution result including transaction hash

application/json
post/api/v1/trade/execute
POST /api/v1/trade/execute HTTP/1.1
Host: api.nansen.ai
apikey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 70

{
  "signed_transaction": "0xdeadbeef",
  "chain": "base",
  "request_id": "text"
}
{
  "txHash": "text",
  "signature": "text",
  "status": "text",
  "ANY_ADDITIONAL_PROPERTY": "anything"
}

Last updated

Was this helpful?