Transaction Submission

Venum accepts your signed transaction and fans it out through its configured landing channels.

Request

POST /v1/swap

{
  "transaction": "SIGNED_TX_BASE64",
  "quoteId": "q_42_1712000000000"
}

What Happens

1. Venum deserializes and verifies the signed transaction
2. Checks the quoteId is valid and not expired (30s TTL)
3. Fans the signed transaction out through the currently configured landing channels
4. Returns the transaction signature immediately

Response

{
  "signature": "5Kx9abc...3nF",
  "status": "submitted",
  "quoteId": "q_42_1712000000000"
}

status: "submitted" means Venum accepted the transaction and started fan-out. It does not guarantee on-chain confirmation — track the signature via GET /v1/stream/tx (landed / processed) or fall back to GET /v1/tx/:signature.

Why Jito?

Standard Solana RPC submission exposes your transaction to standard public relay paths. Many teams prefer bundles or other dedicated submission paths for better landing behavior and lower public exposure. If you do not want to build that plumbing yourself, Venum's transaction sending endpoints can help with the submission step.