Affiliate

Only endpoints that intentionally differ from the standard API carry a chip; the chip links to the note that explains the difference.

Covers the five live routes under /api/dashboard/affiliate. Audience: signed-in dashboard users earning referral commission. Prerequisite for every command below: log in first and keep the session cookie. API keys (ar-…) are rejected on all affiliate routes with 401.

curl -c jar.txt https://atmorouter.dev/api/dashboard/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","password":"..."}'

Two wallets — read this first

There are two balances and money never moves between them on its own:

The affiliate balance reaches the usage balance through exactly one path: an explicit payout with "method":"api_balance", recorded in the affiliate ledger. There is no automatic transfer, no matter how large either balance grows.

1. Check your affiliate balance

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/summary

The response carries your share link and both halves of the picture (identity values below are illustrative; shapes and policy fields are exact):

{
  "code": "K7Q2XA",
  "enabled": true,
  "rate": 0.1,
  "min_withdraw": 5,
  "withdraw_daily": 1,
  "referral_link": "https://atmorouter.dev/?ref=K7Q2XA",
  "rate_history": [{ "rate": 0.1, "effective_from": "2026-09-01T00:00:00Z" }],
  "wallet": { "available": 12.5, "withdrawn": 5.0, "total_earned": 17.5 },
  "stats": {
    "signups": 9, "spenders": 4, "referred_spend": 125.0,
    "matured_pending": 3.2, "locked_pending": 9.3
  },
  "pending_payout": { "id": 41, "amount": 5.0, "method": "usdt" }
}

How to read it:

2. See who you referred

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/referrals
# -> {"data":[{"id":7,"created_at":"...","email":"jo***@example.com",
#      "spent":40.0,"commission":4.0,"matured":1.8}]}

Newest first, capped at 200 entries. Emails are masked server-side to jo***@example.com form (first two local-part characters kept, or customer when no @ exists). spent counts only the referred user's requests that settled with status success or partial — failed requests are never billed, so they never earn commission.

3. Track your payouts

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/payouts
# -> {"data":[{"id":41,"amount":5.0,"method":"usdt","address":"...",
#      "network":"solana","status":"pending","note":"","tx_hash":"",
#      "requested_at":"...","processed_at":null}]}

Newest first, capped at 100 entries. status stays pending until a human operator confirms it (completed) or rejects it (rejected) — there is no intermediate state written by any current endpoint (readers also accept a processing value defensively, but nothing sets it). A populated tx_hash is your on-chain receipt for usdt withdrawals.

Method quirk: only POST creates a payout — any other method on this path (PUT, PATCH, …) returns the list above instead of 405.

4. Read the ledger (beta)

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/ledger
# -> {"data":[{"kind":"payout_usdt","amount":-5.0,"balance_after":7.5,
#      "created_at":"..."}]}

Newest first, capped at 100 entries. Every payout reserves from available_amount and writes a negative-amount entry (payout_usdt or payout_api_balance) with the balance after reservation — the audit trail that ties each withdrawal to the wallet movement. The ledger also records maturation credits (commission_matured), clawbacks (commission_clawed), and reject returns (payout_rejected_return), so a payout entry here always has a matching ledger entry.

5. Request a payout

Two methods, usdt or api_balance (surrounding spaces trimmed, case folded; anything else is a 400). Amounts round to 6 decimals and must be at least the live min_withdraw (currently 5; the server message reads "minimum withdrawal is 5 USDC").

Withdraw to a Solana wallet (manual transfer by an operator follows):

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/payouts \
  -H "Content-Type: application/json" \
  -d '{"amount":12.5,"method":"usdt","address":"<32-to-44-char-solana-address>"}'
# -> {"status":"requested","id":41,"amount":12.5}

Move earnings into API-call credit instead (no address needed, no daily limit):

curl -b jar.txt https://atmorouter.dev/api/dashboard/affiliate/payouts \
  -H "Content-Type: application/json" \
  -d '{"amount":12.5,"method":"api_balance"}'
# -> {"status":"requested","id":42,"amount":12.5}

Check the address twice before sending. The server validates length only (32–44 characters) — it does not verify the address is real or that you typed it correctly, and the operator transfer is irreversible. network defaults to solana.

6. Limits and errors

The server checks, in order: bad body → program enabled → method → amount → minimum → address → wallet lock (a missing wallet stops here) → one in-flight request → daily limit → sufficient balance. The first failure wins. Limit values below reflect current defaults; the summary endpoint always carries the live policy.

Three rules worth remembering:

7. What happens after {"status":"requested"}

Your request is parked as pending. Nothing else moves until a human operator acts — the operator queue is server-side only (there is no public operator endpoint: /api/admin answers 404 on the public gateway):

There is no email-confirmation step on this path: nothing on the payout route sends mail, and no confirmation record is ever read back. Request, then wait. Settlement time depends on operator review, so pending lasting hours is normal.

8. Commission maturity and payout-safety notes

How the money behind this page behaves: the maturity rule, when rate changes take effect, and the payout-safety edges the live service enforces. Nothing here moves money — behavior fixes, if any, ship in a separate lane.