Skip to main content

​
WebSocket

AssetPay provides a Socket.IO WebSocket connection for real-time updates. Use it to push trade status changes and price updates to your frontend without polling.

​
Connecting

Connect using Socket.IO with your API key or a client token: With API key (merchant-level access): 
wss://api.assetpay.co/socket.io/?apiKey=YOUR_API_KEY&EIO=4&transport=websocket
With client token (user-level access): 
wss://api.assetpay.co/socket.io/?token=CLIENT_TOKEN&EIO=4&transport=websocket
Both methods join the same merchant room and receive the same events. Use whichever is more convenient for your architecture.

​
Socket.IO Client Example

import { io } from 'socket.io-client';

const socket = io('wss://api.assetpay.co', {
  transports: ['websocket'],
  query: {
    apiKey: 'YOUR_API_KEY'  // or token: 'CLIENT_TOKEN'
  }
});

socket.on('connect', () => {
  console.log('Connected to AssetPay');
});

socket.on('disconnect', () => {
  console.log('Disconnected');
});

​
Events

​
Trade Updates

Fired whenever a trade changes status. This is the most important event for keeping your UI in sync. 
socket.on('trade', (data) => {
  const trade = data.trade;
  console.log(`Trade ${trade.id} is now ${trade.status}`);
  // Update your UI
});
The data.trade object is the same ITrade shape you see in callbacks and API responses. Trade events are not game-specific. You’ll receive updates for all games (CS2 and Rust) on the same connection.

​
Crypto Deposit Updates

Fired when a merchant crypto deposit changes state: 
socket.on('deposit', (data) => {
  console.log('Crypto deposit update:', data.funding);
});

​
Crypto Withdrawal Updates

Fired when a merchant crypto withdrawal changes state: 
socket.on('withdrawal', (data) => {
  console.log('Crypto withdrawal update:', data.funding);
});

​
WebSocket vs Callbacks

Both WebSocket and callbacks deliver trade updates. They serve different purposes:
WebSocketCallbacks
DirectionPush to your frontend/clientPush to your backend
Use forUI updates, real-time UXBalance operations, business logic
ReliabilityBest-effort (can miss events on disconnect)Guaranteed delivery with retries
StateStateful connectionStateless HTTP POST
Use both. WebSocket for instant UI feedback, callbacks for the authoritative balance updates. Don’t process balance changes based on WebSocket events alone.

​
Connection Notes

  • Only the websocket transport is supported (no HTTP long-polling fallback)
  • The connection authenticates once on connect. If your token expires, reconnect with a fresh one.
  • All events are scoped to your merchant account. You only see your own trades.