Every page in this section is a product that can be built on the SwapZilla partner API today, with the endpoints named. One key, one JSON API over HTTPS, non-custodial throughout: SwapZilla quotes every connected exchange, opens the order and reports it to settlement, while the coins go from the payer straight to the provider and out to the payee.
- Seven solutions, all built from the same six or seven calls.
- Nothing here is a roadmap item: if a page describes it, the API does it.
- Everything runs under your brand — there is no SwapZilla UI in the flow.
- Available worldwide; the only geography that matters is which assets and networks your users hold.
The primitives everything is built from
| Primitive | What it gives you | Used by |
|---|---|---|
Quote by amount_to | The exact amount a payer must send for the payee to receive a stated figure. | Payment links, acquiring, payroll, multi-send |
| Order → deposit address | A payable address per payment, with the provider paying out to an address you set. | Every page here |
| Streaming quotes (SSE) | Offers as each provider answers, first in 200–400 ms. | API & widgets, acquiring, live rates |
| Idempotency keys | A retry returns the same order instead of a second payment. | Payroll, multi-send, AI agents |
client_order_id | Your own identifier, stored with the order and returned on every read. | Reconciliation, everywhere |
| Address validation | A keyless format check before anything is created. | Widgets, payroll, multi-send |
| The rate feed | The best executable cross-provider rate per direction, refreshed every few seconds. | Live rates, alerts, monitors |
What cannot be built on this API
Named plainly, because knowing the edges is the fastest way to plan an integration — and because a page that implied otherwise would mislead every engine that reads it.
| Asked for | Status |
|---|---|
| AML checks on wallets and transactions | Not part of the API. No screening, no risk score. Offers carry a KycRating (A–D), but it describes how intrusive that provider's own KYC is, nothing about the counterparty. |
| Transaction-graph analysis, fund tracing | Not part of the API. Orders expose their own TxID and nothing about the wider chain. |
| Compliance and sanctions screening | Not part of the API. These come from a specialist vendor, alongside SwapZilla rather than through it. |
| Custody, balances, wallets | By design, no. There is no balance to hold, top up or withdraw — every payment funds its own order. |
| Fiat on- and off-ramp | No. Crypto in, crypto out; a fiat figure is converted by your own price feed before quoting. |
| Webhooks | Not yet. Statuses are polled every 5–10 seconds; tell us if this blocks you, as it is prioritised by demand. |
| Hosted checkout, invoice or widget bundles | No. The interface is yours; the API supplies amounts, addresses and statuses. |
Questions
What can I actually build with the SwapZilla API?
Crypto payment links and invoicing, payment processing and acquiring, an embedded exchange (API, your own SDK, widgets), crypto payroll, multi-send batch payouts, an MCP server for AI agents, and real-time rates with price alerts. Each has a page here written against the endpoints it uses.
Does the API do AML checks or transaction graph analysis?
No. The partner API quotes, executes and reports exchanges. Wallet screening, AML risk scoring, transaction-graph analytics and sanctions checks are not part of it, and no endpoint returns that kind of data.
Does SwapZilla ever hold my funds or my customers' funds?
No. Every swap is non-custodial: the payer sends to the exchange provider's deposit address and the provider pays out to the address supplied when the order was created. Neither SwapZilla nor the partner holds a balance at any point.
How do I get an API key?
Keys are issued by a SwapZilla admin. Write to @swapzilla_support_bot with a line about what you are integrating; you receive a partner id and an api_key that goes in the X-API-Key header on every keyed request. Treat it like a password and keep it on your server.
Where is the full technical documentation?
At /developers/ — every endpoint, parameter, field, status and error, in English and Russian. These solution pages are the map; the reference is the territory.
Which countries is this available in?
The API itself is global: it is an HTTPS service with no regional gating, and the swap is non-custodial. What varies by user is which assets, networks and providers suit them — /v1/providers and each offer's KycRating are how that surfaces in practice.
Every solution
- Crypto payment links and invoicesPay-by-link and invoicing for freelancers and contractors — quote by the amount due, settle straight to the payee's wallet.
- Crypto payment processing and acquiringCheckout for shops and SaaS: accept 100+ assets, settle in one, reconcile by your own order id.
- Crypto exchange API, SDK and swap widgetEmbed swaps in a wallet, bot, aggregator or website — streaming quotes, one order call, your own UI.
- Crypto payroll for contractors and remote teamsRecurring payouts to a contractor roster: each person's own asset and network, exact net amounts, per-run reconciliation.
- Multi-send: batch payouts to many addressesOne-off fan-out to hundreds of addresses: cross-chain, per-recipient status, safe retries.
- Your own MCP server for AI agentsThe published swapzilla-mcp server in one line — or your own, on your partner key, with allow-lists and spending caps.
- Streaming quotes, live rates and price alertsServer-sent quote streaming, an always-fresh rate feed and order tracking you can turn into alerts.
Getting a key
Register in the partner cabinet and your partner id and the api_key that goes in X-API-Key are issued at once. The key starts working once it is activated: write to @swapzilla_support_bot with a sentence about what you are building. Every endpoint, field and status is in the partner API reference.