API keys and Rate Limits

​

Creating an API key

1. Sign in to the Relay Dashboard.
2. Open the API keys tab.
3. Click Create key, give it a label (e.g. production, staging), and copy the key.

​

Tracking requests

• Requests — full history of quotes and intents made with each key, with status, route, amounts, and timing.
• Advanced filtering — narrow the table by chain, currency, amount, status, time, and more, combining conditions with AND/OR logic to isolate exactly the requests you care about.
• Custom views — save any combination of filters, sort order, and columns as a reusable view for your team, each with its own name, icon, and color.
• Keys — create, rename, and revoke keys for your account.

​

Default Rate Limits

​

Elevated Rate Limits

​

How to Use an API key

​

HTTP requests

x-api-key: YOUR_API_KEY

​

SDK usage

// Set apiKey only when using the SDK server-side.
import {
  createClient,
  MAINNET_RELAY_API,
} from "@relayprotocol/relay-sdk";

createClient({
  baseApiUrl: MAINNET_RELAY_API,
  apiKey: "YOUR_API_KEY",
  // ...other parameters
});

// Or pass the key per-call via the headers parameter.
import { getClient } from "@relayprotocol/relay-sdk";

const quoteParams = { /* ... */ };

const quote = await getClient()?.actions.getQuote(quoteParams, undefined, {
  "x-api-key": "YOUR_API_KEY",
});

​

Proxy API

import {
  createClient,
  MAINNET_RELAY_API,
} from "@relayprotocol/relay-sdk";

createClient({
  baseApiUrl: "https://my-proxy.relay.link", // Replace with your proxy endpoint
  // ...other parameters
});

​

Keeping Your API key Secure

• Keep it server-side only — never expose it in client-side or frontend code. Use a proxy API if calling Relay from the browser.
• Use environment variables — store the key in environment variables, not hardcoded in source code.
• Don’t commit it to version control — add it to .gitignore or use a secrets manager.
• Restrict access — only share the key with team members who need it.
• Rotate regularly — create a new key in the Relay Dashboard and revoke the old one whenever a team member with access leaves.