ghostswap-partners-api

GhostSwap Partners API integration

You are helping a developer integrate the GhostSwap Partners API — a server-to-server REST API for non-custodial crypto-to-crypto swaps. The developer's end-users send funds to a deposit address GhostSwap returns; the destination wallet receives the swapped funds. GhostSwap handles all upstream liquidity, signing, and clearing. The partner earns a 0–4 % markup (chosen at application time) on every completed swap, paid out in USDT once balance ≥ $100.

This skill is the single document you need to produce a working end-to-end integration. Read it once, then write code.

---

When to use this skill

Trigger when the developer's request involves any of:

• Adding a crypto exchange widget, swap form, or "convert X to Y" flow to their app
• Accepting one crypto and crediting the user in a different one
• Quoting live exchange rates for a pair (e.g. BTC → ETH)
• Earning affiliate commission on referred swaps (the ?ref=<slug> flow on ghostswap.io)
• Building a Telegram bot, Discord bot, or wallet plugin that does crypto-to-crypto
• Specifically mentions "GhostSwap", "ghostswap.io", "partners.ghostswap.io", gspk_live_*, or gssk_live_*

Do not trigger for fiat on/off-ramps, custodial trading APIs, or self-custodial DEX SDKs — those are different products.

---

Architecture, in one sentence

Your server holds the bearer token; your server proxies every call to https://partners-api.ghostswap.io; your browser code talks only to your server.

The bearer must never reach the browser. Browser code calls /api/quote, /api/swap, etc. on the developer's own server; the server adds Authorization: Bearer ${PUBLIC_KEY}:${SECRET} and forwards to GhostSwap.

---

Step 0 — Get a credential (one-time, by the developer)

The developer (not the agent) must do this once:

1. Sign in at https://partners.ghostswap.io/sign-up.
2. Submit the application form (org name, website, expected monthly volume, chosen partner fee 0–4 %).
3. Wait for admin approval (~24 h). Once status flips to active, an activation email lands in their inbox.
4. Open /dashboard/api-credentials → click Create live credential → copy both values:
   • GHOSTSWAP_PUBLIC_KEY — looks like gspk_live_<32 hex>, always recoverable from the dashboard.
   • GHOSTSWAP_SECRET — looks like gssk_live_<48 hex>, shown once at creation; can be revealed later via the audit-logged Reveal secret button.
5. Set both as environment variables on the developer's server. Never paste them into code that ships to the browser.