Skip to main content

​
Forkast Data API

🔴 This API surface is actively being wired up. Names, filters, and even full routes may evolve before the public release.
The Forkast Data API exposes the portfolio, market, and builder analytics that power the Forkast prediction markets. Every route mirrors the interfaces our internal analytics teams rely on, but the data originates from Forkast-run subgraphs, caches, and databases so we can guarantee freshness and uptime.

​
Base URL and format

  • Hostname: https://data-api.forka.st
  • Protocol: HTTPS only; responses are JSON.
  • Authentication: Not required for read operations. Rate limiting will be enforced once the API goes into production.
  • Specification: All requests and sample payloads live inside api-reference/openapi-data-api.json, which powers the panel on the right-hand side of each page.

​
Endpoint families

TopicDescriptionSample endpoints
HealthReadiness probes for monitors.GET /
PortfolioPosition snapshots, historical exits, and wallet totals.GET /positions, GET /closed-positions, GET /value, GET /traded
Market metricsAggregate stats derived from Forkast liquidity.GET /holders, GET /oi, GET /live-volume
ActivityHistorical fills and ledger-like user activity.GET /trades, GET /activity
BuildersEarly endpoints that will summarize third-party builder performance.GET /v1/builders/leaderboard, GET /v1/builders/volume

​
Usage tips

  1. Prefer market filters when you have known condition IDs. The API accepts CSV lists (market=0xabc,0xdef) using standard form encoding (explode=false).
  2. Pagination is handled with limit and offset pairs. Lower values keep response times predictable while the cache is still maturing.
  3. Builder routes are placeholders until the attribution ETL ships; expect empty arrays for now.
As the ingestion jobs stabilize we will remove the warning banner above and expand these docs with live examples.