Skip to main content
GET /api/v1/events returns a paginated list of public trading events.

​
Supported filters

  • traderIds
  • assetIds
  • directions
  • types
  • startTime
  • endTime
  • limit
  • cursor

​
Example: filter by asset

​
Example: time-bounded query

​
Default time range

  • If startTime and endTime are both omitted, the API may apply a bounded default window.
  • If an explicit startTime is earlier than the accessible window, the API can clamp it forward.
  • The actual bounds used for the response are returned in data.meta.appliedTimeRange.

​
Pagination rules

  • Pass cursor from meta.nextCursor to advance to the next page.
  • Pagination is forward-only.
  • Cursors remain usable if matching events disappear between requests because of deletion or eligibility changes.
  • Later pages may omit rows that disappeared after an earlier fetch.
  • Pagination reflects the current eligible set and is not a frozen snapshot.
  • limit accepts up to 200.

​
Event classification flags

Event rows include three boolean classification flags: Agents and product clients should not present assumed=false or autoGenerated=false as meaningful user-facing attributes. The absence of a flag is the normal case.

​
Hydrating context

Event rows expose compact references:
  • positionId for the related position
  • messageId for the related Source Message ID when available
  • traderId and assetId for discovery hydration
Use GET /api/v1/positions?positionIds=... for position performance and GET /api/v1/messages?ids=... for source-message text or attachments.
Last modified on June 19, 2026