0trace
Get API

Referral links

Drive traffic at /r/{code} with the swap direction encoded in the URL. You earn your revenue share automatically.

A second integration model alongside the signed Partner API: send traffic at a short link. Your default referral link is ready the moment your cabinet is — no code required. The visitor lands on the homepage, and any order created in that browser session is attributed to you — with no backend on your side. Optional codes let you split traffic by channel.

URL contract

Template
https://0trace.io/r/{code}?from={FROM}&to={TO}

{code} is either your default referral id (shown in your cabinet — the simplest link, no setup) or the public string of a code from /api/v1/codes (the same code you use as the suffix in X-API-KEY: prefix.code). {FROM} and {TO} are asset IDs from /api/v1/currencies (e.g. btc, xmr, usdt_trc20). Both are optional; missing or unknown values fall back to the homepage defaults.

Default link (your referral id)
https://0trace.io/r/8f3kd0aZ91xQ?from=usdt_trc20&to=btc
Code link (optional, per channel)
https://0trace.io/r/desktop?from=usdt_trc20&to=btc

How traffic flows

  1. Visitor follows your link. We resolve it — your referral id, or a code — to your partner and the asset IDs, set an HMAC-signed cookie carrying partnerId (plus codeId when it is a code link), and 302 to the homepage with the requested pair pre-filled.
  2. The visitor proceeds through the standard swap flow. The cookie rides along on the order-create request.
  3. On order creation we re-validate the cookie: your partner must be enabled, and — for a code link — the code must be enabled too. We then attach attribution to the order. Earnings accrue against your account in real time.

Pairing with the XML rate feed

Most listing integrations pair this URL with our XML rate feed. Scrape the feed at /api/rates.xml; each <item> carries the asset IDs you substitute into the URL template per row.

Earnings model

Referral traffic earns your revenue share of our service fee. The visitor sees our live rate — your share comes out of our fee, not theirs. The exact percentage is set on your partner record and shown in your cabinet.

Markup — your own margin on top of our rate — applies only to the signed API (X-API-KEY: prefix.code), where you render the marked-up rate in your own interface. It is not applied to referral-link traffic.

Attribution lifetime

The cookie is HttpOnly, signed with HMAC-SHA256, and lives for 30 days. Last-touch model: a subsequent visit through a different partner’s link overwrites the cookie with the newer attribution. A cookie that survives past TTL, belongs to a disabled partner, or carries a now-disabled code is rejected at order-create time without partner credit.

Kill switch and rotation

Your default referral link follows your partner status: it earns whenever your account is enabled and stops the moment the operator disables it. Code links add per-channel control on top — disable a code from /api/v1/codes/enable or the cabinet to stop new attributions for that channel immediately. Existing in-flight cookies stop earning the moment the code (or your partner) is disabled — re-enabling restores future earnings without re-issuing links. To retire a code permanently, disable it and issue a new one alongside.

Privacy

Bad codes, disabled codes, and unknown asset IDs all 302 to the homepage with no cookie set — the response is identical to a hit with no code at all. The cookie payload contains only opaque internal identifiers; no email, IP, or user-agent data is stored. The capture endpoint is per-IP rate limited to prevent enumeration.

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