Launch a crypto exchanger with one API โ€” how EIDEX Merchant API works

byโ€ข

Building a crypto exchanger? Hereโ€™s what our new Merchant API can save you from doing yourself

Hey Product Hunt community ๐Ÿ‘‹

We just published a deep dive on our Crypto Merchant API โ€” the backend layer we built for teams launching crypto exchangers, P2P services, payment gateways, or trading bots.

The idea is simple: instead of spinning up your own liquidity, running blockchain nodes, and rebuilding order matching from scratch, you plug into one HTTP API and focus on your product.

What the Merchant API handles:

๐Ÿ”น Quotes & orders โ€” real-time pricing across supported pairs (BTC, ETH, USDT, SOL, XRP + 15 networks), MARKET and LIMIT execution

๐Ÿ”น Deposit addresses from a shared pool โ€” reserve an address by nonce, release it back when done. Same nonce returns the same address, so retries donโ€™t break your logic

๐Ÿ”น HMAC-signed webhooks โ€” real-time deposit.confirmed and withdraw.completed events, no polling needed

๐Ÿ”น Granular permissions โ€” API keys with READONLY / TRADING / WITHDRAW scopes. A stolen READONLY key canโ€™t drain funds

๐Ÿ”น IP whitelist (CIDR) โ€” configurable per key

๐Ÿ”น Idempotency keys โ€” required for POST /order and POST /withdraw, makes retries safe on money operations

๐Ÿ”น Rate limits โ€” 60 req/min per key, up to 10 keys per account

A typical exchange flow is just 6 API calls:

GET /tickers โ€” pull rates for the storefront
POST /address/reserve โ€” reserve a deposit address by nonce
Client sends funds โ†’ you receive the deposit.confirmed webhook
POST /order โ€” execute with Idempotency-Key
GET /order/{id} โ€” track status
POST /withdraw โ†’ withdraw.completed webhook โ†’ POST /address/release

Integration scenarios weโ€™ve documented:

โ€ข Classic web exchanger โ€” your storefront, our settlement layer

โ€ข Telegram bot โ€” same logic, no frontend needed

โ€ข White-label exchanger โ€” your brand, our infra hidden behind it

Full docs, OpenAPI spec for Postman/Insomnia, and quickstart โ†’

Discussion prompt for the community:

For those of you whoโ€™ve built (or considered building) a crypto product โ€” whatโ€™s usually the biggest bottleneck? Liquidity access, compliance, or infrastructure?

And for those whoโ€™ve integrated third-party APIs: what would actually make you choose a merchant API over building in-house? Curious to hear real trade-offs from builders here.

10 views

Add a comment

Replies

Be the first to comment