Skip to main content
GET
/
api
/
v1
/
reports
cURL
curl -sS \
  -H 'Authorization: Bearer $OXI_SK' \
  'https://api.0xinsider.com/api/v1/reports?granularity=daily&period=2026-02-17'
{
  "object": "list",
  "data": [],
  "has_more": false,
  "next_cursor": null,
  "total": 0,
  "meta": {
    "request_id": "req_example",
    "cached": false
  }
}
One route for every report granularity. Pass granularity (daily, weekly, or monthly) and the matching period token, and the response is byte-identical to the legacy /api/v1/reports/{daily,weekly,monthly} route for the same window. The period token shape depends on the granularity:
  • daily: a UTC date, YYYY-MM-DD.
  • weekly: an ISO week YYYY-WW, or a from,to pair of YYYY-MM-DD dates.
  • monthly: a calendar month, YYYY-MM.
curl -H "Authorization: Bearer $OXINSIDER_API_KEY" \
  "https://api.0xinsider.com/api/v1/reports?granularity=daily&period=2026-05-08"
The per-granularity caps match the legacy routes (daily 50, weekly 100, monthly 200), and the three legacy routes stay live. Snapshots carry trust metadata, so partial or unavailable sections are explicit. The singular Daily, Weekly, and Monthly routes return the same bodies.

Authorizations

​
Authorization
string
header
required

API key: Authorization: Bearer oxi_sk_live_... for live data (requires an active Insider subscription), or oxi_sk_test_... for sandbox/test mode (free account, deterministic fixture data, no live rows). Both key classes use the same paths; the prefix selects live vs sandbox.

Query Parameters

​
granularity
enum<string>
required

Report granularity selector.

Available options:
daily,
weekly,
monthly
​
period
string
required

Period token for the granularity. daily: UTC date YYYY-MM-DD. weekly: ISO week YYYY-WW, or a from,to YYYY-MM-DD pair. monthly: UTC month YYYY-MM.

Minimum string length: 1

Response

Daily report snapshot

​
object
string
required
Allowed value: "report_snapshot"
​
data
object
required
​
meta
object
required