> ## Documentation Index > Fetch the complete documentation index at: https://docs.raze.bot/llms.txt > Use this file to discover all available pages before exploring further. # Server-Sent Events > One live channel as `text/event-stream`. The frames are the WebSocket's; the SSE event name is the frame `type` (`snapshot`, `trade`, `retract`, `candle`, …), so listen with `addEventListener(type, …)`. A comment line every 15 s keeps the connection open. Bad parameters answer `400` JSON before the stream starts; while the server is at capacity, a new stream answers `503` (`server_busy`, `Retry-After: 30`), and streams already open keep running. One channel per connection, same frames as the WebSocket. The SSE event name is the frame `type`, so `EventSource.onmessage` does not fire: listen with `addEventListener("snapshot", …)`, `addEventListener("trade", …)` and so on. See the [SSE guide](/streaming/sse). ## OpenAPI ````yaml GET /v1/stream/{channel} openapi: 3.1.0 info: title: Raze Market Data API version: 1.0.0 description: > Multichain market data for tokens, trades, charts, holders, launchpads and wallets on Solana, Ethereum, BNB Chain, Base and Robinhood Chain, as REST snapshots and live streams. **Conventions, everywhere:** - Chains: `sol`, `eth`, `bsc`, `base`, `robinhood` (aliases `solana`, `ethereum`, `bnb`, `hood` and network ids work too). - EVM addresses are answered lowercase; Solana addresses are case-sensitive. - Amounts in USD end in `Usd`; percents are 0–100 and end in `Percent`; times are Unix **milliseconds**. - A value nobody knows is `null`, never `0`. - Success: `{"data": …}`, plus `"next"` on paged lists (pass it back as `cursor`, as given). A page can hold fewer rows than `limit`, even none, and still carry `next`: a list ends only where `next` is `null`. - Failure: `{"error": {"code", "message"}}` with status 400 (`bad_request`), 401 (`unauthorized`), 404 (`not_found`), 429 (`rate_limited`), 502 (`upstream_unavailable`), or 503 with a `Retry-After` header (`upstream_unavailable` on a page to ask for again, `server_busy` on a new live connection). - A Solana address that does not decode to a 32-byte key is a 400 wherever one token or wallet is named. Lists (`/v1/tokens?ids=`, `/v1/prices?tokens=`) leave out an id that looks like a Solana address (32 to 44 base58 characters) but is not a 32-byte key; an id that does not look like an address still fails the whole list with 400. **Auth:** send your key as `x-api-key`, `Authorization: Bearer `, or `?apiKey=` (for WebSocket and EventSource, which cannot set headers). `/health` and `/v1/openapi.yaml` need no key. **Live:** one WebSocket at `/v1/ws` carries any number of channels (also at `wss://ws.raze.bot`); the same channels are available one per connection as Server-Sent Events at `/v1/stream/{channel}`. Every channel sends a `snapshot` frame first, then changes. servers: - url: https://api.raze.bot description: Production security: - ApiKeyHeader: [] - Bearer: [] - ApiKeyQuery: [] tags: - name: catalog description: Health, chains and token search - name: tokens description: Token snapshot, trades, candles, holders, top traders, image - name: discovery description: Trending, screener and launchpad boards - name: wallets description: Wallet leaderboard, stats, holdings, PnL and swaps - name: prices description: Native coin prices and token prices - name: live description: WebSocket and Server-Sent Events paths: /v1/stream/{channel}: get: tags: - live summary: Server-Sent Events description: > One live channel as `text/event-stream`. The frames are the WebSocket's; the SSE event name is the frame `type` (`snapshot`, `trade`, `retract`, `candle`, …), so listen with `addEventListener(type, …)`. A comment line every 15 s keeps the connection open. Bad parameters answer `400` JSON before the stream starts; while the server is at capacity, a new stream answers `503` (`server_busy`, `Retry-After: 30`), and streams already open keep running. operationId: openStream parameters: - name: channel in: path required: true schema: type: string enum: - trades - candles - token - launchpad - prices - wallet - name: chain in: query schema: type: string - name: token in: query schema: type: string - name: interval in: query description: '`candles` only' schema: type: string - name: unit in: query description: '`candles` only' schema: type: string enum: - usd - marketCap - name: board in: query description: '`launchpad` only' schema: type: string enum: - new - graduating - graduated - name: wallet in: query description: '`wallet` only' schema: type: string responses: '200': description: An event stream content: text/event-stream: schema: type: string example: > event: snapshot data: {"channel":"trades","chain":"sol","token":"","type":"snapshot","data":[…]} event: trade data: {"channel":"trades","chain":"sol","token":"","type":"trade","data":{…}} '400': $ref: '#/components/responses/BadRequest' '503': $ref: '#/components/responses/Busy' components: responses: BadRequest: description: A parameter is missing or wrong content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: bad_request message: 'unknown chain ''xyz'', use one of: sol, eth, bsc, base, robinhood' Busy: description: >- The server is at capacity and refuses new live connections; open ones keep running. Connect again after `Retry-After` seconds headers: Retry-After: schema: type: integer example: 30 content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: server_busy message: the server is at capacity, retry in 30 s schemas: Error: type: object properties: error: type: object properties: code: type: string enum: - bad_request - unauthorized - not_found - rate_limited - upstream_unavailable - server_busy message: type: string securitySchemes: ApiKeyHeader: type: apiKey in: header name: x-api-key Bearer: type: http scheme: bearer ApiKeyQuery: type: apiKey in: query name: apiKey ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.