Introduction
REST is enough to place a trade. For a live book — ticks, open P/L, and position changes — you typically use two feeds. Chart ticks come from the public market socket /ws/markets (same as Trade, no OAuth). Account, position, and contract updates for the signed-in user come from the Partner WebSocket after you have an access token.
The Partner WebSocket is scoped to that authorized user. It is not a feed of every referred trader. Partner-wide fills and commissions belong on webhooks.
Bootstrap the socket
For index candles and last price, open wss://api.coinpes.com/ws/markets (locally ws://localhost:8082/ws/markets) and subscribe with { "action": "subscribe", "symbol": "VOL75" }. That path is public.
- For the authorized user,
POST /v1/ws-tokenwith the Bearer token. The response includes a short-lived bootstrap token andws_url. - Open that URL. Locally the gateway is often port 8001; production typically uses
wss://on the API host. - Subscribe only to the channels the screen needs (quotes for the visible symbol, account, positions). Unused channels waste battery and make reconnects heavier.
What to show in your UI
- Mid, bid, and ask for the symbol on screen.
- Open CFD positions and live P/L.
- Open contracts until they settle.
- Wallet balance after fills and settlements.
Prefer socket updates for animation. After any gap, trust REST for the official list of positions and balances so a missed tick cannot leave a ghost row.
Reconnects
Treat the socket as ephemeral. If it drops, mint a fresh ws-token and reconnect. Do not reuse an expired bootstrap token. Then reconcile: list positions and accounts over REST so you do not miss a fill that happened while disconnected.
Back off on repeated failures. A tight reconnect loop will hit rate limits and look like an outage to the user.
Webhooks vs the socket
If you also run a partner backend, do not expect this connection to tell you that a referred trader on another device just settled a contract. Subscribe to contract.settled (and Test it in Referrals) for that.
The WebSocket is for the authorized user, not a dump of every referred trader. Partner-wide events belong on webhooks.
Message shapes: WebSocket reference.
Frequently asked questions
Can I reuse a ws-token after disconnect?
Does the socket include every referred trader?
What should I do after a drop?
Related guides
6 MINUsing the Partner API
What the Partner API is for, how a user session works, and what still lives in the Referrals dashboard.
6 MINConnect users with OAuth
Let traders sign in or register on Coinpes with OAuth 2.0 and PKCE, then exchange the code on your server.
6 MINPlace trades from your app
List wallets, send idempotent CFD orders, and open timed contracts with a user access token.
8 MINReceive webhook events
Register HTTPS endpoints in Referrals, verify HMAC signatures, Test a signed delivery, and process events once.
5 MINTest in sandbox
Use partner_test clients and demo accounts to finish OAuth, trades, sockets, and webhooks safely.
6 MINClone and deploy the example app
Clone the Partner API example from GitHub, reskin it, and deploy the Vite app from Vercel with your OAuth client.
5 MINKeep credentials safe
Where secrets belong, which tokens to rotate, and how partner routes handle trader PII.
6 MINPartner API reference
Full Partner API reference: OAuth, trading routes, WebSocket, webhooks, and OpenAPI.