{
"id": "<string>",
"type": "insider_radar_flag_raised",
"created_at": "2023-11-07T05:31:56Z",
"data": {
"trade_id": 123,
"wallet": "<string>",
"trader_id": 123,
"condition_id": "<string>",
"suspicion_score": 123,
"size": 123,
"price": 123
}
}insider_radar_flag_raised
Sends suspicious_trade_flagged under its older name, to endpoints that registered that name.
{
"id": "<string>",
"type": "insider_radar_flag_raised",
"created_at": "2023-11-07T05:31:56Z",
"data": {
"trade_id": 123,
"wallet": "<string>",
"trader_id": 123,
"condition_id": "<string>",
"suspicion_score": 123,
"size": 123,
"price": 123
}
}insider_radar_flag_raised is the older name of suspicious_trade_flagged: one event under two names, with the same data. An endpoint receives the name it registered.
The Webhooks guide covers signatures, retries, and replay.Authorizations
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).
Scopes
Headers
v1= followed by the hex HMAC-SHA256 of {timestamp}.{raw body} under the endpoint signing secret. During a staged secret rotation, or while 0xinsider rotates the key every signing secret is derived from, it carries up to four comma-separated v1= candidates, the current secret's first: accept the delivery when any one verifies.
Body
Response
Return any 2xx status to acknowledge the delivery. Any other status, a redirect, a timeout or a connection error is retried on the published retry policy.
Was this page helpful?