RAVN Integrator API

RAVN aggregates RFQ market makers, intent networks, and cross-chain solvers behind a single, uniform interface. You can quote, execute, and track a swap across EVM, Solana, and native Bitcoin, and your users always receive the real token, never a wrapped copy.

Quickstart

Swap 1 ETH to SOL end to end in four calls.

Collecting your fee

Charging a fee? The four steps that decide whether a swap pays you.

Execution types

The one field your integration branches on.

API Reference

Every endpoint, request, and response.

Base URL

https://app.ravn.exchange/api/v1

Content type: application/json
Amounts: always strings, in the token’s smallest unit (wei, lamports, satoshis).
Native coin: use the sentinel 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE. For Solana native SOL, use its mint So1111...1112.

Every call works with no x-api-key header at all if you just want to try it, but get a free key first if you can. It’s instant, no review, and quadruples your rate limit. See Authentication for the full tier breakdown. RAVN itself charges 0 bps, always. Integrators set their own swap fee on their key and get paid their share; every quote reports the applied fee. A swap pays you once your code pays any fee the execution asks for and reports the swap to /status until it is final: see Collecting your fee and Pricing.

Why it is different

Most swap APIs do one thing, an EVM transaction, so their whole surface assumes it. RAVN spans three genuinely different execution models, and every quote resolves to exactly one executionType. Your integration reads that one field and branches. That is the whole contract.

Model	What the user does	Venues
`TRANSACTION`	Sign and broadcast	Across, Relay, Mayan, Eco Routes, THORChain, Jupiter, 0x Swap, 0x Solana, Nordstern, Fly Trade, KyberSwap, OKX DEX, Bebop, Layerswap, Hinkal
`SIGNATURE`	Sign typed data (no gas), then RAVN submits	0x Gasless, Bebop, CoW, Relay
`DEPOSIT`	Send the origin asset to an address	NEAR Intents, Chainflip, Rift, Houdini Swap, Layerswap, Relay (BTC)

See Supported Chains & Venues for which type each venue returns and when: a few depend on the source chain or execution mode. Hinkal, a private venue you opt into, first asks the paying wallet for two signatures (AUTHORIZE) before its TRANSACTION: see Execution Types.

The response envelope

Every response has the same shape.

{ "data": { }, "meta": { "requestId": "uuid", "version": "2024-01" } }

{ "error": { "code": "NO_LIQUIDITY", "message": "..." },
  "meta": { "requestId": "uuid", "version": "2024-01" } }

Every response also carries x-request-id and ravn-version headers. Log the requestId and quote it when you contact support.