> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launchblitz.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# API

> LaunchBlitz transaction WebSocket API for authenticated launch and trade execution.

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

```text theme={null}
wss://tx.launchblitz.ai
```

Use the [connection guide](/api/connection) for authentication, keepalives, and a minimal client.

## Supported platforms

| Platform            | Methods                                                                                                   | Page                                          |
| ------------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| `pump_fun`          | `create_with_image_url`, `create_with_image_blob`, `buy`, `sell`, `collect_creator_fee`                   | [Pump.fun](/api/pump-fun)                     |
| `pump_swap`         | `buy`, `sell`                                                                                             | [PumpSwap](/api/pump-swap)                    |
| `raydium_launchpad` | `create_with_image_url`, `create_with_image_blob`, `sell`                                                 | [Bonk.fun / Raydium launchpad](/api/bonk-fun) |
| `bags`              | `create_with_image_url`, `create_with_image_blob`                                                         | [Bags](/api/bags)                             |
| `heaven`            | `create_with_image_url`, `create_with_image_blob`                                                         | [Heaven](/api/heaven)                         |
| `liquid_af`         | `create_with_image_url`, `create_with_image_blob`                                                         | [Liquid AF](/api/liquid-af)                   |
| `four_meme`         | `create_with_image_url`, `create_with_image_blob`, `create_with_image_url_and_transaction`, `buy`, `sell` | [Four.meme](/api/four-meme)                   |
| `clanker_base`      | `create_with_image_url`, `create_with_image_blob`                                                         | [Clanker](/api/clanker)                       |
| `nad_fun`           | `create_with_image_url`, `create_with_image_blob`                                                         | [Nad.fun](/api/nad-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](/api/generic-transactions) for the shared request shape, [TXResponses](/api/tx-responses) 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.