Admin & FLEX Options

Stream real-time administrative (admin) messages for options via WebSocket, including OPRA FLEX trade notifications. Each message delivers the raw administrative text along with its exchange, sequence number, and nanosecond SIP timestamp.

FLEX (FLexible EXchange) options are customized, exchange-traded options contracts that let counterparties negotiate non-standard terms — such as the strike price, expiration date, exercise style, and settlement type — beyond what standard listed options offer. FLEX trades are disseminated by OPRA as administrative messages and surfaced through this feed.

Use Cases: FLEX trade monitoring, market operations tracking, data auditing.

Options BasicFree

Options Starter$29/mo

Options Developer$79/mo

Options Advanced$199/mo

Options BasicFree

Options Starter$29/mo

Options Developer$79/mo

Options Advanced$199/mo

Plan AccessIncluded in select Options plans

Options BasicFree

Not included

Options Starter$29/mo

Not included

Options Developer$79/mo

Not included

Options Advanced$199/mo

Real-time

Options BasicFree

Not included

Options Starter$29/mo

Not included

Options Developer$79/mo

Not included

Options Advanced$199/mo

Real-time

Plan RecencyReal-time

Plan HistoryNot applicable

Parameters

exchange_id

string

required

Specify an exchange ID or use * to subscribe to admin messages from all exchanges. To subscribe to more than one exchange, send a comma separated list with the channel prefix on each entry, for example `AD.302,AD.323`. See Exchanges for Massive's mapping of exchange IDs.

Response Attributes

enum (AD)

The event type.

string

The unique identifier for this admin message, composed of the SIP timestamp and the sequence number (e.g., "1793911442930568079-4043826282").

integer

The exchange ID. See Exchanges for Massive's mapping of exchange IDs.

string

The administrative message text as distributed by OPRA.

integer

The SIP timestamp in Unix nanoseconds.

integer

The sequence number represents the sequence in which admin events happened. These are increasing and unique, but will not always be sequential (e.g., 1, 2, 6, 9, 10, 11).

Code Examples

# Connect to the websocket
npx wscat -c wss://socket.massive.com/options

# Authenticate
{"action":"auth","params":"YOUR_API_KEY"}

# Subscribe to the topic
{"action":"subscribe", "params":"AD.*"}

Subscription Request

Response Object

{
  "ev": "AD",
  "i": "1793911442930568079-4043826282",
  "t": 1793911442930568200,
  "q": 4043826282,
  "x": 302,
  "m": "TEXT CFLEX SPY LST PM EUR 4 LEGS 1 @ 733.36"
}