https://data.rekt.trading serves settled trades and ended positions, rebuilt by replaying each settlement
through the same engine the program runs. It is read-only, it needs no account, and CORS is open, so
a browser can call it directly. Start at GET /v0/health.
The program is the ground of truth and this API is a lagging mirror of it. It answers no live
question. Read live state from the chain through the SDK.
Routes
Limits
- Per-transaction history is the last 48 hours.
/v0/trades,/v0/minute/roundsand/v0/positionsreturn rows settled or ended in the last 48 hours. A round that is still open is dated by when it opened. A page that asks for older rows is empty./v0/trades/{signature}answers404for a trade older than that, the same answer as for a signature it does not hold.totalMatching,matchedandnextBeforeSlotcount only the rows inside the window. The response states the window in itswindowfield. - Pages hold at most 100 rows. A larger
limitis read as 100. Page withbeforeSlot, usingnextBeforeSlotfrom the previous page. - 60 requests a minute per client, with a burst of 20. Over that the API answers
429and aRetry-Afterheader with the number of seconds to wait. Wait that long, then retry. - Days with fewer than 3 settlements are merged into the day after them in
byDay,volumeByDayand the day series of/v0/capital, and the response says so indayCells. A merged day takes the label of the day it joined, and nothing is lost: the cells still sum to the total. - Aggregates are cached for 10 seconds.
/v0/stats,/v0/marketsand/v0/capitalcarryCache-Control: public, max-age=10, stale-while-revalidate=30. Poll them no faster than that. The per-transaction routes cache for 5 seconds.
GET /v0/health returns these figures for the caller that asked, under access. Read the limits from
there instead of copying them.
History longer than 48 hours
- Totals and trends:
/v0/statsreturnsbyDay(settlements per day) andvolumeByDay(per day: settlements, stake and notional)./v0/marketsreturns the all-time settlements, stake and notional per market. Both cover the whole archive. - One trader’s older trades, or one older trade: read them from the chain.
readTradeHistoryin the SDK scans a trader’s closed trades from the program’s own events.
