Skip to main content
Endpoints fall into four buckets by how they treat history. The window is enforced by the query layer, not by request parameters, so calling with a wider since than the underlying source allows will silently return data only as far back as the source goes.

​
Rolling 90-day window

Lifecycle-derived endpoints. Underlying aggregates are refreshed hourly. Querying beyond 90 days returns no rows.

​
All-time / lifetime

Reads the trader’s full indexed history (since Coinversa began indexing the wallet). No cap.

​
Caller-bounded via since

Window is whatever the caller passes. Defaults vary; see the per-endpoint reference for each. The since parameter accepts a number + unit (m, h, d — weeks are not a unit; 2w is rejected with a 400 invalid since format). Values beyond 90 days are silently clamped to 90 days; within that, the effective maximum is bounded by the underlying data freshness for each endpoint, not by your tier.

​
Builder analytics windows

The builder endpoints use their own window parameters, enforced server-side like everything else on this page: The since clamp is silent: the response’s window field echoes what you requested even when the data was clamped to 90 days — same truncation-detection advice as above: compare response timestamps against your requested window. Underlying history: builder-fee orders and attributed fills are complete and gapless from 2025-01-25. Trigger-order (stop/TP) fill capture went live 2026-08-20 with backfill to 2026-03-24 and earlier history in progress — until it completes, attributed metrics slightly undercount vs ledger revenue (disclosed in every response’s dataNotes). Ledger revenue itself is cumulative on-chain data with no window floor. The clamps above are per-request query windows, not data floors — retention’s 12-month triangle reads the full order history. See Builder codes & attribution.

​
Live / real-time

Current snapshot only. No historical concept. Each call returns the latest state from the indexer.

​
FAQ

The 90-day cap balances refresh cost (full lifecycle reconstruction is expensive) and storage against the analytical window most consumers actually need. Backtests and behavior-pattern studies rarely care about positions older than a quarter; trend-detection consumers care about the last few weeks.
Yes — longer windows are available on Enterprise. Contact chat@coinversa.ai with the wallet set and time range you need; one-off bulk exports and recurring custom-window endpoints are both possible.
  • Aggregates (lifecycles, cohort rollups, discovery endpoints): refreshed hourly.
  • Trades, closed positions, raw events: written as they’re indexed, typically within seconds of the L1 fill.
  • Live endpoints: current state of the indexer, 1–10s behind L1 depending on the metric.
The query runs against the available data and returns whatever it has. No error is raised. Compare your response timestamps against your requested since to detect truncation.