Skip to main content
GET
cURL
This is the deprecated alias of Suspicious trade. It reads the same ids and returns the same data object, plus a Deprecation header reading @1790121600 (2026-09-23T00:00:00Z) and a Link header naming the canonical route for your own id with rel="successor-version" and the versioning policy with rel="deprecation". This route stays live with no retirement date, and no Sunset header is sent. Its envelope stays object: "radar_flag", on purpose, so a client that branches on the envelope is unaffected here. The canonical route answers object: "suspicious_trade". A flag is a review target, not proof of insider trading. Use this route when a reader opens one flag from an alert or a review queue. The response has the same shape as one row of Insider Radar, which is the route for ranking many at once.

Parameters

Key response fields

Example

What it does not return

  • Proof of insider trading. The flag says one trade matched a heuristic worth a human look, and nothing more.
  • A freshly computed score. Every value here is the one stored when the trade was scored.
  • The trade itself. The same raw whale_alerts.id opens it on Whale trade, with size_usd, price, side, and the wallets on the other side.

Caching

Send the ETag from a response back in an If-None-Match header. If the flag has not changed, you get 304 Not Modified with an empty body.

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
If-None-Match
string

Conditional GET validator from a previous ETag. Matching values return 304 Not Modified with an empty body.

Path Parameters

id
string
required

Raw whale_alerts.id or rf_-prefixed radar flag id.

Response

Radar flag

object
string
required
Allowed value: "radar_flag"
data
object
required
meta
object
required