New Transactions

Subscribe

Request Body

Parameter	Type	Description
method*	string	Must be "subscribe"
subscription*	object	See below
subscription.type*	string	Must be "newTransactions"

Note: No user parameter required for global subscriptions.

Response

Subscription Confirmation:

{
  "channel": "subscriptionResponse",
  "data": {
    "method": "subscribe",
    "subscription": {
      "type": "newTransactions"
    }
  }
}

Transaction Notification:

{
  "channel": "newTransactions",
  "data": {
    "transactionId": "0x1234...",
    "type": "OrderPlaced",
    "timestamp": 1701234567890,
    "blockNumber": 12345,
    "txIndex": 0,
    "orderId": "0x5678...",
    "data": {}
  }
}

Transaction Fields

Field	Type	Description
transactionId	string	Unique transaction hash
type	string	Transaction type
timestamp	number	Transaction time in milliseconds
blockNumber	number	Block containing transaction
txIndex	number	Transaction index within block
orderId	string	Related order ID (if applicable)
data	object	Type-specific transaction data

Transaction Types

Type	Description
OrderPlaced	New order submitted to system
OrderCanceled	Order canceled
OrderFilled	Order executed
Deposit	Funds deposited
Withdrawal	Funds withdrawn
Transfer	Internal transfer
FundingPayment	Funding rate payment
InterestPayment	Interest payment
Liquidation	Position liquidation
PositionModified	Position TP/SL updated

Unsubscribe

{
  "method": "unsubscribe",
  "subscription": {
    "type": "newTransactions"
  }
}

Notes

• Global subscription - no user address required
• High volume stream - can produce many messages per second
• Includes all system transactions
• Consider client-side filtering for performance