Public API and Embed Widget
The CoinKong public API exposes read-only quote, coin, pair and order status data as cached JSON, and the swap widget can be embedded on another page. It is intended for people who want to show CoinKong comparisons in their own interface without building a separate exchange integration.
What the endpoints return
Quote and rate responses contain the offers that were genuinely available for the requested pair, with provider names, expected output, fee details and network information. Coin and pair lists describe what can be routed right now rather than a static catalogue. Order status returns the public stage of a swap keyed by its CK reference.
Responses are cached for a short window so a burst of visitors does not turn into a burst of provider calls. They are rate limited, so poll sensibly and reuse a response until it expires instead of requesting it on every render.
- No account or API key is needed for the public read endpoints
- Provider secrets are never sent to the browser
- Order lookups use the opaque CK reference, not an internal id
- CORS friendly JSON for a widget or a small dashboard
Embedding the widget
The embed keeps the same manual deposit flow as the main site: the visitor picks an offer, sends from their own wallet to the address shown, and receives the payout at the address they entered. It does not require a connected wallet, custody or signing credentials.
If you embed the widget, keep the surrounding page clear about who runs the swap. CoinKong is a comparison front end, and the provider named on the selected offer is the one that receives the deposit and performs the conversion.
Good practice
Treat a quote as a short-lived snapshot. Re-read it before displaying a call to action, handle the case where no route is available, and never present a cached number as a guaranteed rate. The API is a convenience layer over live provider quotes, not a price oracle for settlement.