Raze.bot Developers

API Types

Every Raze.bot endpoint requires an API key. There is no unauthenticated tier.

Trading

/swap/sol/buy, /swap/sol/sell, /swap/sol/buy-sell, /swap/sol/sell-buy
/swap/sol/quote/:mint, /swap/sol/quote/stream (WebSocket), /swap/sol/instructions
/perp/sol/*

Data

History (https://api.raze.bot/api/sol/*), Streaming (wss://ws.raze.bot/ws/sol), Solana RPC (https://rpc.raze.bot)

Fees

The router adds no fee of its own. Tip and platform fee come from your request (tipWallet/tipLamports, feeWallet/feeBps) — omit them and the built transaction carries neither. feeBps is capped on-chain at 1000 (10%) and is charged only on routes that go through the Raze CPI router.

Authentication

Pass your API key via header or query parameter:

// API key required — via Authorization header
const response = await fetch(
  `https://router.raze.bot/swap/sol/quote/${mint}`, {
    headers: { 'Authorization': `Bearer ${apiKey}` }
  }
);

// Or via X-API-Key header
const response2 = await fetch(
  `https://router.raze.bot/swap/sol/quote/${mint}`, {
    headers: { 'X-API-Key': apiKey }
  }
);

Response Format

All APIs return JSON with a consistent structure:

{
  "success": true,
  "data": { ... }
}

Error responses:

{
  "success": false,
  "error": "Error message",
  "message": "Detailed description"
}

HTTP Status Codes

Code	Description
200	Success
400	Bad Request - Invalid parameters
401	Unauthorized - Invalid or missing API key
404	Not Found - Resource doesn’t exist
429	Rate Limited - Too many requests
500	Server Error - Internal error
504	Gateway Timeout - Request timed out

Transaction Flow

For swap operations, the typical flow is:

Request Transaction

Call the buy/sell endpoint to get unsigned transaction(s)

Sign Transaction

Sign the transaction with your wallet’s private key

Send Transaction

Submit via the Raze Solana RPC relay (POST /tx) or any standard Solana RPC endpoint

Best Practices

Secure Your Keys

Store API keys in environment variables
Never expose private keys in code
Use .gitignore for sensitive files

Handle Errors

Always check success field in responses
Implement retry logic with exponential backoff
Log errors for debugging

Optimize Performance

Use the nearest server region
Cache quotes when appropriate
Batch transactions when possible

Manage Slippage

Set appropriate slippage for volatile tokens
Default slippage is usually sufficient for stable pairs
Higher slippage for low-liquidity tokens

Next Steps

Portal Setup

Get your API key

Rate Limits

Understand usage limits

My Raze

Changelog

Development Basics

API Types

Trading

Data

Fees

Authentication

Response Format

HTTP Status Codes

Transaction Flow

Best Practices

Next Steps

Portal Setup

Rate Limits

​API Types

​Trading

​Data

​Fees

​Authentication

​Response Format

​HTTP Status Codes

​Transaction Flow

​Best Practices

​Next Steps

Portal Setup

Rate Limits

API Types

Trading

Data

Fees

Authentication

Response Format

HTTP Status Codes

Transaction Flow

Best Practices

Next Steps