DocsReference

API and realtime data

Use cursor-paginated REST endpoints for discovery and history, then direct contract reads for authoritative live state.

API conventions

Growing lists accept limit (1–100) and an opaque cursor. Return the nextCursor unchanged on the next request and stop when it is null.

Response

{
  "items": [],
  "nextCursor": null
}

Configured API

https://api.v2.yeeld.fun

API reference OpenAPI JSON

Core resources

/v1/tokens — launches, search, filters, and sorting.
/v1/tokens/:token — launch configuration and status.
/v1/tokens/:token/curve-trades and /trades — venue-specific activity.
/v1/tokens/:token/candles — aggregated curve and v4 candles.
/v1/tokens/:token/locks, /reward-claims, /bribes — reward activity.
/v1/accounts/:account/locks — account lock history.
/v1/buybacks — public schedules and execution history.
/v1/protocol/revenue and /yeeld-burns — flywheel accounting.
/v1/pairs and /v1/baskets — current launch configuration choices.

Realtime stream

Connect to /v1/stream for insert notifications covering trades, reward accruals, and YEELD burns. The frontend uses these events to invalidate the relevant React Query caches rather than treating WebSocket payloads as complete authoritative records.

Hybrid reads

Use indexed data for lists and history. Use eth_call for current reserves, earned rewards, roles, allowance, balances, and eligibility.