Skip to main content
LaunchBlitz exposes a WebSocket API for transaction execution. The socket accepts authenticated JSON text frames, dispatches them into the backend transaction handlers, and streams request progress back as structured responses.

​
Endpoint

wss://tx.launchblitz.ai
Use the connection guide for authentication, keepalives, and a minimal client.

​
Supported platforms

PlatformMethodsPage
pump_funcreate_with_image_url, create_with_image_blob, buy, sell, collect_creator_feePump.fun
pump_swapbuy, sellPumpSwap
raydium_launchpadcreate_with_image_url, create_with_image_blob, sellBonk.fun / Raydium launchpad
bagscreate_with_image_url, create_with_image_blobBags
heavencreate_with_image_url, create_with_image_blobHeaven
liquid_afcreate_with_image_url, create_with_image_blobLiquid AF
four_memecreate_with_image_url, create_with_image_blob, create_with_image_url_and_transaction, buy, sellFour.meme
clanker_basecreate_with_image_url, create_with_image_blobClanker
nad_funcreate_with_image_url, create_with_image_blobNad.fun

​
Message flow

  1. Open a WebSocket with ?key=YOUR_API_KEY.
  2. Wait for the initial connected text frame.
  3. Send a JSON text frame with platform, type, and the fields required by that method.
  4. Handle streamed responses such as ingress_ack, dispatch, submit, mint, confirmed, failure, or error.
Use generic transactions for the shared request shape, TXResponses for streamed responses, then go to the platform page you need. These pages follow the methods wired into the transaction_socket service itself. They intentionally document the registered handlers exposed by the socket, not every transaction enum that may exist elsewhere in the backend codebase.