A crypto swap API lets a wallet, exchange, or fintech product offer coin-to-coin conversions without operating its own liquidity, custody, or compliance stack. The integrator passes the user's source coin, destination coin, and receiving address to the API; the provider quotes a rate, generates a deposit address, watches for the deposit, and forwards the converted asset to the destination. The integrator never touches funds.
TL;DR: The GhostSwap API exposes the same non-custodial swap engine that powers ghostswap.io — 1,600+ pairs across 200+ supported assets, floating-rate pricing, and p50 settlement of ~8 minutes — with a partner revenue-share model for wallets that route volume through it.
A crypto swap API is a REST/JSON interface that programmatically performs cross-coin swaps. Unlike an exchange API (which assumes the user has an account and a balance with the exchange), a swap API treats every transaction as a one-shot, non-custodial conversion: deposit in, swap, withdraw out.
Why wallets integrate a swap API instead of building one
Building your own swap engine means sourcing liquidity, managing inventory risk, building order routing across centralised and decentralised venues, and operating the compliance posture that each of those venues requires. For a wallet team focused on UX, that's the wrong fight.
A swap API collapses that work into a few HTTP calls. Your users get in-wallet swaps; you get a revenue line that didn't exist before; and the swap provider absorbs the operational complexity. This is the same pattern that several Monero-native wallets have used to offer in-app on-ramps from BTC, ETH, or stablecoins into XMR — Feather Wallet (desktop) and Monerujo (Android) are commonly cited examples of wallets that have published third-party swap integrations in their release notes.
The trade-off is straightforward: you give up direct control of the swap economics in exchange for not having to build them. A well-structured revenue-share program is what closes that loop.
How the GhostSwap API works end-to-end
GET /v1/pairs— list the 1,600+ supported pairs. Filter by source or destination asset.GET /v1/rate?from=BTC&to=XMR&amount=0.05— fetch a floating-rate quote. Quotes are indicative; final rate is set at the moment your user's deposit confirms.POST /v1/swap— create a swap. You supplyfrom,to,amount,destination_address, and an optionalrefund_address. The response contains a one-time deposit address.- User sends the deposit. Your wallet UX displays the address, QR code, and the indicative receive amount.
GET /v1/swap/{id}— poll for status. Lifecycle isawaiting_deposit→received→exchanging→sending→complete.- Funds arrive at the user's destination address. Typical end-to-end settlement is p50 ~8 minutes, p95 ~30 minutes.
There is no account creation step for the end user, no KYC, no email — the integrator authenticates with an API key, and the user supplies only the destination address.
How GhostSwap compares to other swap APIs
| Feature | GhostSwap API | ChangeNOW API | SimpleSwap API |
|---|---|---|---|
| Pair count | 1,600+ (product-truth, 2026-05-16) | ~900 (their site, retrieved 2026-05-16) | ~1,500 (their site, retrieved 2026-05-16) |
| End-user KYC for swaps | None required | None required for standard flow | None required for standard flow |
| Custody model | Non-custodial pass-through | Non-custodial pass-through | Non-custodial pass-through |
| Pricing | Floating-rate from aggregated liquidity | Floating + fixed options | Floating + fixed options |
| Partner revenue share | Yes — see below | Yes | Yes |
Comparison is descriptive, not evaluative. Partners should verify current numbers on each provider's site before signing.
The partner revenue-share model
GhostSwap pays a share of swap revenue back to integrating wallets and apps. The share scales with monthly routed volume — higher volume tiers receive a higher percentage. Payouts are made in the partner's choice of supported assets (typically BTC, ETH, USDT, or XMR) on a monthly cadence.
Three practical notes for evaluating the program:
- Attribution is API-key-scoped. Every swap created with your partner key is attributed to you for the lifetime of that swap. There's no cookie window or referral-link fragility.
- You set the user-facing rate. Partners can add a markup to the quoted rate; the markup accrues to the partner in addition to the base revenue share.
- No exclusivity required. You can run GhostSwap alongside other providers and route per-pair based on which gives your users the best rate.
GhostSwap is not a registered financial service. The partner program is a commercial integration; partners are responsible for their own jurisdictional obligations.
When the GhostSwap API is the right fit
It's the right fit if:
- You operate a non-custodial wallet and want in-app swaps without holding user funds.
- Your users care about not creating accounts or submitting ID for routine swaps.
- You want a single API that covers BTC, ETH, XMR, LTC, stablecoins, and 1,600+ pair combinations — not just EVM-to-EVM.
- You'd rather get a revenue line than build liquidity infrastructure.
It's the wrong fit if:
- You need fiat on-ramps inside the same API call (GhostSwap is crypto-to-crypto).
- You need fixed-rate quotes locked at quote time (GhostSwap is floating-rate; the rate is set when the deposit confirms).
- Your jurisdiction or product requires you to KYC every swap user — that's a layer you'd build on top, not below.
FAQ
Q: How does the no-KYC model work for the API integrator?
A: The end user supplies a receiving address; GhostSwap routes the swap non-custodially and never holds their funds. The integrator authenticates with an API key. Neither the user nor the integrator submits identity documents to GhostSwap for swap operations.
Q: What are the typical settlement times?
A: Per current product telemetry, p50 is around 8 minutes end-to-end and p95 is around 30 minutes. Times depend on source-chain confirmation requirements — Bitcoin deposits inherit Bitcoin confirmation times.
Q: How is the revenue share calculated?
A: It's a percentage of GhostSwap's swap revenue on transactions attributed to your API key, paid monthly. The exact tier breakdown is shared during partner onboarding. Partners can also add their own markup on top of the quoted rate.
Q: Can I use the API to build a full no-KYC exchange front end?
A: Yes. The API surface covers pair discovery, quoting, swap creation, and status polling — enough to power a complete swap UI. Many partners ship a swap tab inside an existing wallet rather than a standalone exchange.
Q: Is the API documented publicly?
A: Yes — see the GhostSwap API reference for endpoints, parameters, response shapes, and example payloads.
Get started
If you're evaluating swap APIs for a wallet or app integration, the fastest path is to read the API reference and try a test swap against the live swap engine on the homepage to see the end-user flow your integration will produce.
For partnership terms, reach out via the contact page.
