Skip to main content
The Etherfuse API is organized around REST. It has predictable, resource-oriented URLs, accepts and returns JSON, and uses standard HTTP verbs and response codes. Every endpoint on the pages that follow includes a live “Try it” playground and copy-paste code samples.

​
Two API surfaces

The reference is split into two groups:
  • Ramp API (/ramp/*) — the authenticated partner operations: onboarding, quotes, orders, swaps, customers, wallets, KYC, webhooks, and organizations. Requires an API key. Start with List assets.
  • Lookup API (/lookup/*) — public reference data: exchange rates, stablebonds, bond costs, and country codes. No API key required. Start with List stablebonds.

​
Base URLs

EnvironmentBase URL
Sandboxhttps://api.sand.etherfuse.com
Productionhttps://api.etherfuse.com
Build and test against the sandbox first — see Initial Setup. The endpoints are identical across environments; only the base URL and API key differ.

​
Authentication

Send your API key in the Authorization header — with no Bearer prefix. Full details and the sandbox-vs-production key rules are in Authentication. 
curl https://api.sand.etherfuse.com/ramp/assets \
  -H "Authorization: <your_api_key>"

​
Conventions

Errors

Standard HTTP status codes (400, 401, 403, 404, 409, 5xx) with a human-readable message.

Pagination

POST list endpoints take {pageNumber, pageSize, filters} and return a page envelope.

Idempotency

You supply resource UUIDs; reusing one returns 409 instead of creating a duplicate.

Webhooks

Signed, real-time events for orders, swaps, KYC, and bank accounts.

​
Use the spec directly

Download openapi.json to import into Postman or Insomnia, or to generate a client. Prefer natural language? Connect the MCP server.