A no-KYC crypto swap API lets a wallet, dApp, or service embed crypto-to-crypto swaps without collecting identity documents from the end user. The integrator passes a swap request — source coin, destination coin, amount, and a receiving address — and the API returns a deposit address and a quote. The GhostSwap API requires no KYC from end users: wallet builders pass swap requests through, and no user identity data is collected or stored by GhostSwap. End users need no account and no email to initiate a swap.
TL; DR: The GhostSwap API exposes 1,600+ crypto pairs with no end-user account, no email, and no identity verification. Funds pass through non-custodially. You integrate against the REST endpoints, your users swap, and you earn a revenue share on volume.
A no-KYC swap API is a programmatic endpoint that creates and settles crypto-to-crypto exchanges without verifying the end user's identity. Unlike a centralised exchange API, it is non-custodial: the funds route through a swap engine rather than into an account held by the provider.
What is a no-KYC swap API and who uses one?
A no-KYC swap API is the integration layer behind an in-app "swap" or "exchange" button. Your wallet calls it; it returns a quote and a deposit address; your user sends funds; the swap settles to the user's destination address. No account is created on the provider's side, and no identity verification is requested from the end user.
The typical integrators are non-custodial wallet developers, portfolio apps, and DeFi front-ends that want swap functionality without building liquidity or running an exchange. They care about three things: coin coverage, settlement reliability, and whether the provider forces KYC onto their users.
GhostSwap fits this slot directly. It is a no-KYC crypto exchange: no account, no email, no signup required for the end user. It supports 1,600+ coins via the API across BTC, ETH, XMR, SOL, and altcoin networks. Median swap completion is roughly 8 minutes, with a 95th-percentile time near 30 minutes depending on chain congestion.
The non-custodial model matters for liability. Funds pass through the swap engine and are never held by GhostSwap. For a wallet developer, that means you are not routing your users into a custodial account they have to trust with their balance.
Step-by-step: integrate GhostSwap's API with no user KYC required
The integration flow mirrors the product's own swap UI. Each step is a single API call.
- Request an API key — sign up as a partner and get a key. See the GhostSwap API reference for the endpoint list and authentication.
- Fetch supported pairs — query the pairs endpoint to populate your in-app picker. 1,600+ pairs are available, so most wallets filter to the coins they already hold.
- Obtenez un devis — pass source coin, destination coin, and amount. The API returns a floating-rate quote drawn from aggregated liquidity from leading crypto markets.
- Create the swap — submit the user's destination address and (optionally) a refund address. The API returns a deposit address.
- Have the user send funds, then poll status — your app shows the user the deposit address; once funds arrive, the swap routes and settles to the destination. Median settlement is ~8 minutes.
No step in that flow asks the end user for an identity document, email, or account. The user supplies only a receiving address and a refund address. Funds pass through non-custodially and are never held by GhostSwap.
For wallet teams that want to test the live flow before wiring the API, the consumer widget d'échange sur la page d'accueil runs the same engine. You can watch a real BTC-to-XMR swap settle end to end, then replicate it programmatically.
GhostSwap API vs ChangeNOW, SimpleSwap, Godex — KYC requirements compared
The table below compares end-user KYC posture and integration model. Competitor rows are drawn from each provider's own public API/documentation pages, retrieved 2026-06-12 — verify current terms against the linked source before you build, as policies change.
| Caractéristique | Échange de fantômes | Change maintenant | Échange simple | Godex |
|---|---|---|---|---|
| End-user account required | Aucun | Voir provider docs | Voir provider docs | Voir provider docs |
| Modèle de garde | Passage sans garde | Per provider docs | Per provider docs | Per provider docs |
| Pairs exposed via API | 1,600 | Per provider docs | Per provider docs | Per provider docs |
| Modèle de tarification | Liquidités agrégées à taux variable | Per provider docs | Per provider docs | Per provider docs |
| Typical settlement | ~8 min median, ~30 min p95 | Per provider docs | Per provider docs | Per provider docs |
The one claim worth stating plainly: GhostSwap collects no identity data from your end users. Wallet builders pass swap requests through; no user identity data is collected or stored. For the competitor columns, check each provider's linked documentation — KYC thresholds and "enhanced verification" triggers differ and change, and we won't assert specifics we can't source.
Common integration pitfalls for wallet developers
A few mistakes recur when teams wire up a swap API for the first time.
- Skipping the refund address. Floating-rate swaps settle at the price when funds arrive, not when the user clicked. If a deposit underpays or arrives late, the refund address is how the user gets funds back. Make it a required field in your UI.
- Hard-coding pairs. The supported set is large and changes. Pull the pairs list at runtime rather than shipping a static array, or your picker will drift out of sync.
- Hiding the floating-rate nature. Tell users the quote is indicative. Floating rate means the price at the moment funds arrive, typically within the quoted spread. Hiding this generates support tickets.
- Not polling status to completion. Show the user each state — awaiting deposit, confirming, exchanging, sending, done. A silent spinner during a ~8-minute settlement reads as a stuck transaction.
Revenue share and partner terms: what wallet builders should know
Wallet developers integrating a swap API generally want two things from the commercial side: a revenue share on swap volume and terms that don't push KYC onto their users. GhostSwap's partner model is built for non-custodial wallets and apps that want swap functionality plus a cut of the spread on routed volume.
If you are comparing partner programs, evaluate them on: the share structure (flat vs. tiered by volume), settlement of partner earnings, coin coverage, and whether the provider's terms require your end users to verify identity. Competing services such as SimpleSwap and SwapSpace also publish partner/affiliate programs — review their current terms directly, since revenue-share rates and payout mechanics change and we won't quote competitor figures we can't source.
For GhostSwap, the partner pitch is straightforward: 1,600+ pairs, non-custodial pass-through, no end-user KYC, and a revenue share on the volume your integration drives. Start from the GhostSwap API reference to scope the integration, then reach out via the partner contact to discuss share terms.
QFP
Q: Which crypto swap APIs do not require KYC for the end user?
A: The GhostSwap API requires no KYC from end users — no account, no email, no identity verification to initiate a swap. Other providers differ; check each one's API documentation, because KYC thresholds and verification triggers vary and change over time.
Q: Is a no-KYC swap API non-custodial?
A: It can be. GhostSwap's API is non-custodial — funds pass through the swap engine and are never held by GhostSwap. The user supplies a destination address and a refund address; settlement goes directly to the destination.
Q: How many pairs can I expose through the GhostSwap API?
A: 1,600+ pairs across BTC, ETH, XMR, SOL, and altcoin networks. Pull the pairs list at runtime so your in-app picker stays current.
Q: How long does a swap take to settle via the API?
A: Median completion is roughly 8 minutes, with a 95th-percentile time near 30 minutes depending on chain congestion. Poll the status endpoint and surface each state to your user.
Q: Do wallet partners earn revenue from swaps?
A: Yes. GhostSwap offers a revenue share to wallet and app partners on the swap volume their integration drives. Start with the API reference, then contact the partner team to scope share terms.
Construit le
If you are adding swaps to a wallet or app and don't want to push KYC onto your users, scope the integration against the GhostSwap API reference, then test the live flow with the swap widget and pair pages like Conversion d'ETH en XMR et BTC à XMR.
GhostSwap is not a registered financial service. Questions about partner terms go through the page contact.
