Skip to main content
GET
Merchant Monitor Stream (event_v1)

Overview

Use this WebSocket endpoint to receive realtime merchant events (for example: invoice updates, payments, and commerce order events where applicable).

Authentication

WebSocket connections use a token minted from the REST API. See: Mint a WebSocket Token.

Request

WebSocket URL (wss)

Response

WebSocket upgrade returns 101 Switching Protocols. After connecting, you receive frames (for example event_v1 events). Example event frame:

Errors

  • 401 invalid/expired ws_token (connection is rejected/closed)
  • Treat delivery as at-least-once; dedupe by event.id if you process idempotently.

Examples

  • Use since=<event_id> to resume from a known cursor when supported.
Next: Merchant Invoices

Authorizations

x-api-key
string
header
required

API key for server-to-server operations (scope=merchant or commerce)

Query Parameters

token
string

Short-lived ws_token (browser/mobile auth).

since
string

Replay cursor (event id), e.g. evt_1700000000000-123.

types
string

Comma-separated allowlisted event type filters (e.g. invoice.*, invoice_payment.updated).

invoice_type
string

Optional invoice type filter (e.g. standard, commerce).

customer_id
string
invoice_id
string
environment
enum<string>
Available options:
devnet,
mainnet
format
enum<string>
Available options:
event_v1

Response

101

Switching Protocols (WebSocket)