Cross-Chain Swap API for Wallets and Apps

Quick answer

The RAVN Integrator API lets wallets, dapps, bots, and agents add cross-chain swaps without integrating every venue separately. You send a quote request, receive a ranked route with an opaque quoteToken, then execute and poll status.

Base URL: https://app.ravn.exchange/api/v1
Auth: header x-api-key (issued by RAVN)

Core endpoints

• POST /quoteBest-execution route + opaque quoteToken
• POST /executeTurn quoteToken into an execution payload
• POST /submit-signatureSubmit signed orders for SIGNATURE venues
• GET /statusNormalized swap status
• GET /tokens/resolveToken metadata
• GET /healthPer-venue liveness (public)

Full reference: docs.ravn.exchange and for integrators.

Execution types

Every winning route collapses to one field:

• TRANSACTION: sign and broadcast the returned transaction
• SIGNATURE: sign typed data; RAVN or the venue submits
• DEPOSIT: send the origin asset to a venue-generated address (common for native BTC and some intent rails)

Amounts are strings in smallest units (wei, lamports, satoshis).

What corridors the API can serve

• Native BTC either direction when Garden, Relay, or NEAR Intents quote
• Solana via Jupiter Ultra, Relay, NEAR Intents
• EVM same-chain RFQ via 0x Gasless, Bebop, CoW when available
• EVM cross-chain via Across, Relay, Mayan Swift
• HyperEVM and Robinhood Chain when listed and venues quote

See supported chains and tokens for the network map.

Fees (API vs app)

Direct users of the consumer app pay zero RAVN markup. Integrator API fees are route-based bps and appear in the quote. Published tiers include higher bps on native BTC routes than same-chain EVM. Always read the live quote.

Typical integration flow

1. Resolve tokens and confirm venue health.
2. POST /quote with origin, destination, amount, and recipient rules for your product.
3. Show the user net out, costs, and ETA from the normalized quote.
4. POST /execute with the quoteToken; branch on executionType.
5. Collect signatures or prompt deposit as required.
6. GET /status until success, failure, or refund.

FAQ