Skip to main content
GET
cURL
Read this endpoint before choosing event_types for Create a webhook or Update a webhook. It returns the same event catalog for every key. The webhook guide describes all 16 types and their payload fields.

Key response fields

The 16 event types

These pairs are aliases with identical payloads and access rules:
  • large_trades_inserted and whale_trades_inserted
  • trader_synced and whale_trader_synced
  • suspicious_trade_flagged and insider_radar_flag_raised
  • sharp_money_flow_detected and smart_money_flow_detected
Subscribe with either spelling. Listing both on 1 endpoint stores 1 subscription. Deliveries keep your registered spelling in the delivery row, the x-0xinsider-event-type header, and the payload’s type.

Example

What it does not return

  • Anything about your account. The catalog is identical for every key, and it never says which types you subscribe to.
  • A JSON Schema. payload_shape is a one-line string. For a whole delivery, read What a delivery carries.
  • A dormant type. All 16 listed types are active. The status field stays in the response, because a future type can be listed before its deliveries start.
  • Event deliveries or live data in this catalog. Subscribe to events to receive their payloads. large_trade_inserted_v2 includes a trade; the count events require a follow-up Large trades request.
  • Private browser events. Alerts, following, radar, and position-cache changes inside the 0xinsider site are not webhook event types.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict

Response

Webhook event catalog

object
string
required
Allowed value: "list"
data
object[]
required
has_more
boolean
required
meta
object
required
next_cursor
string
total
integer