This guide walks you through making your first Relayer API call. You will verify connectivity with the health endpoint, then make an authenticated request.Documentation Index
Fetch the complete documentation index at: https://docs.relayer.fi/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- An API key from your operator dashboard (see Authentication)
curlor Node.js installed
Environments
Relayer provides two environments. Choose the one that matches your stage:| Environment | Base URL | Use for |
|---|---|---|
| Sandbox | https://testnet.relayer.fi/v1 | Testing and development |
| Production | https://api.relayer.fi/v1 | Live operations |
Step 1: Verify connectivity
Start with the unauthenticated root endpoint to confirm the API is reachable.- Sandbox
- Production
200 with a basic service descriptor.
Step 2: Set up your environment
Store your API key and base URL as environment variables:- Sandbox
- Production
Step 3: Make an authenticated request
Now make an authenticated call. This example lists the wallets in your workspace — a safe, read-only operation that confirms auth, scope, and module activation in one go.Step 4: Explore the Kits
Now that you are authenticated, explore the Kit that matches your use case:Signing Kit
Create self-custodial wallets and sign transactions with passkeys.
Payout Kit
Set up fiat on/off-ramp rails and manage recipients.
Agent Kit
Ship budget-enforced AI agents that can sign and pay for resources.
Widget Kit
Embed canonical swap, transfer, and crosschain widgets in your app.
Troubleshooting
| Problem | Solution |
|---|---|
Connection refused | Check RELAYER_BASE_URL — sandbox: https://testnet.relayer.fi/v1, production: https://api.relayer.fi/v1 |
401 Unauthorized | Verify your Authorization header uses ApiKey prefix (not Bearer) |
404 Not Found | Check the endpoint path starts with /v1/ |
| Slow first response | Sandbox cold-starts after idle (30-60s). Production does not have this delay. |