Recurring event cycles
/api/v1/events/{slug}/cyclesThin rows for the cycles of a RECURRING_PROPOSITION event: the live and unsettled cycles (up to 50, newest first), then the 49 soonest upcoming cycles, then the 50 newest settled cycles. Fetch GET /markets/{id} for a cycle's full market. Empty for other event types and for price-range events, whose cycles are all in the event detail markets[]. Concurrent reads of the same event share one query per API instance. Archived events 404.
Path Parameters
Event slug (any event in the group).
Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/v1/events/string/cycles"{ "cycles": [ { "id": "string", "slug": "string", "display_label": "string", "state": "DRAFT", "exchange": "AGARA", "condition_id": "string", "token_ids": [ "string" ], "reference_at": "string", "observe_at": "string", "cadence_seconds": 0, "result_label": "string" } ]}Resolve event slug to canonical URL GET
Returns the category-rooted URL an event slug should redirect to. Child slugs in a group resolve to the group root. Archived events 404.
Event detail GET
Returns the event + its group markets + curated "see also" relations + leaf category paths. Most event types ship every market in the group; RECURRING_PROPOSITION events serve a window: the live cycle group uncapped, up to 50 newest unsettled cycles, 49 soonest upcoming cycles, and 50 newest settled cycles - whole cycles only. With slim=true, a recurring up/down event keeps only its live and unsettled cycles; list the rest with GET /events/{slug}/cycles. A child-event slug resolves to its group root — clients should compare slug on the response and redirect to the canonical URL if it differs. Archived events 404.