ripper.funDocs

Where would you like to start?

↑ ↓ to navigate Enter to open · Esc to close
Open app ↗
Browse documentation ⌄
Docs/Developers

REST API reference

The HTTP routes available to applications and integrations.

Conventions

Production base URL: https://ripper.fun/api/v1. Send JSON for POST bodies. Token reads generally use chain and mint; mint means the token address on the specified chain. For token amounts expressed in raw units, send a decimal integer string to avoid precision loss.

Read token data

Klines return OHLCV history where available. Trades and holder data depend on the token’s indexed coverage and caller access. The stream endpoint uses Server-Sent Events; it is separate from the JSON MCP endpoint.

http
GET /api/v1/tokens/search?q=QUERY&chain=solana
GET /api/v1/token/klines?chain=solana&mint=TOKEN_ADDRESS&interval=1m&limit=100
GET /api/v1/token/trades?chain=solana&mint=TOKEN_ADDRESS
GET /api/v1/token/holders?chain=solana&mint=TOKEN_ADDRESS
GET /api/v1/token/stream?chain=solana&mint=TOKEN_ADDRESS

Quotes and transaction building

Both routes accept token, side, amount, and chain inputs through their JSON request bodies. Use mint, side, amountInRaw, slippageBps, and chain. The build route requires the signed-in wallet; a quote is not an executed trade. Review and sign returned transactions with the correct wallet.

http
POST /api/v1/trade/quote
POST /api/v1/trade/build

Accounts and key management

http
GET /api/v1/me
GET /api/v1/keys
POST /api/v1/keys
DELETE /api/v1/keys?id=KEY_ID

Authentication details

Handle errors

Check HTTP status before reading a success payload. Common responses include 400 for invalid input, 401 for a missing wallet session, 404 for missing or paused resources, 409 for state conflicts, and 429 for rate limiting. Follow Retry-After when present. Do not automatically retry wallet transactions without checking their chain status.

Keep exploring