0trace
Get API

Overview

What the Partner API does, who it is for, and the shortest possible integration path.

Private, invite-only. Small surface: every endpoint is one signed POST, every webhook is one signed event. A self-serve cabinet lives at /partner/login. /api/v1/create accepts an Idempotency-Key so retries are safe. See Authentication for the signing rules.

New here? Start at the Quickstart: first signed call, first order, first webhook in five minutes.

Two integration models

  • Server-to-server API. Sign every request, control price quoting and idempotency, receive signed webhooks. Start at the Quickstart.
  • Referral links. Send traffic at /r/{code} with the swap direction in the URL. No backend integration; earnings accrue automatically. See Referral links.

How it fits together

  • Discovery. /api/v1/currencies and /api/v1/pairs. Unauthenticated; served from a 30-second cache.
  • Quoting. /api/v1/price. Unauthenticated; recomputed per request against live rates.
  • Order lifecycle. /api/v1/create to open, /api/v1/order to poll, /api/v1/emergency to resolve status = "EMERGENCY", /api/v1/qr for a pay-in QR.
  • Reference codes. /api/v1/codes (POST / GET / DELETE) and /api/v1/codes/enable for multiple reference codes with per-code markup. Your API key and secret are always available in your cabinet.
  • Push contracts. Webhooks (signed, opt-in per-partner subscription) and XML rate feeds (public, unauthenticated).
  • Self-service portal. Partner cabinet at /partner/login: dashboard, orders, payout history, your keys, your referral link, and your codes.

Versioning

The wire contract is stable. Breaking changes are announced 30 days in advance to the contact email on your partner record. Backwards-compatible additions (new endpoints, new optional fields, new opt-in webhook events) land at any time and never break an existing integration.

Payout isolation

Partner credentials authorise discovery, quoting, and order creation. They cannot move funds. Payouts run on a separate service that re-verifies the on-chain deposit before broadcasting.

Partner API.
Same engine as 0trace.

A private partner integration surface. Signed quotes, server-side pricing, webhook delivery, multiple reference codes, and a self-serve cabinet — all backed by the production exchange engine.

Need help?

Questions? Answers.

A partner integration surface on top of the same exchange engine that powers 0trace.io. You connect with a signed REST contract, query quotes, open orders, and receive webhook notifications. Our liquidity, our pricing, our payouts. You focus on your product.
No. The API is private and invite-only, aligned with the privacy posture of 0trace itself. There is no KYC, no identity collection, and no source-of-funds reporting required of partners or their end users.
Submit a request through our partner application form at 0trace.io/api/contact-sales and we’ll reply within three business days.
Traffic is encrypted in transit (TLS). Every request is signed with HMAC-SHA256 over the exact request body bytes and gated by a nonce-based replay window. Pricing, fees, and payout amounts are computed server-side. Payouts run on an isolated service that re-verifies each transfer against the on-chain deposit before broadcasting.
A per-partner sliding-window weight budget, default 2500 wu/min (≈50 creates/minute). Endpoint weights: /api/v1/create is 50, /api/v1/qr is 5, every other endpoint is 1. XML feeds run on a separate public bucket. Exceeding the budget returns 429 with a Retry-After header. To raise your cap, send your projected per-endpoint call rate to your operator contact.
Two ways to earn. Revenue share: send us traffic with your referral link and earn a share of our service fee on every order — the visitor sees our live rate. Markup: integrate through the API and add your own margin on top of our rate, shown in your own interface. Use either, or both.
Yes. 0trace operates its own liquidity pool across every supported asset and network. Quotes are recomputed server-side at order creation against the live feed. Payouts are direct, with no third-party intermediary.
Bitcoin, Ethereum, BSC, Solana, Tron, Monero, and Arbitrum One — covering native coins plus the major stablecoins on each network (USDT, USDC, USDC.e).
Yes. We push signed events for order.status_changed and partner.paid_out; you subscribe to the ones you want in your cabinet.

Follow us on X for the latest updates.

Subscribe

Guides

Pairs

Terms