/api/v1/indices/{id}/membership-eventsGETRecent membership events for an NFL team index, newest first: admissions (a market became its sleeve's active member) and settlements (a member's market resolved and its final value was booked). Indices without sleeve membership return an empty list. Returns the
{data, meta} envelope. Not paginated: meta.total counts the rows in this response and has_next is always false.Authorization
bearerAuth *Bearer <token>
Session token from the app, or an API key (the
ak_ prefix), sent as a Bearer token or an ?api_key= query parameter.. Token in: headerQuery Parameters
per_page?integer
Rows returned in this response (1-100), newest first.
Default:
20Min: 1Max: 100Response
200 · Rows, newest first
data *object[]
Show item properties
kind *"admission" | "settlement"
The event type.
occurred_at *string (date-time)
When the event took effect.
sleeve?stringnull
The sleeve the event belongs to, when resolvable.
market_id *string
The market the event is about.
display_ticker *string
Display label for the market.
name?stringnull
The market's question. Omitted when the market is unknown.
settled_price?numbernull
For a settlement, the booked final value (0 or 100). Omitted for admissions.
meta *object
400 · The `from` date is after the `to` date.
error?string
Stable, machine-readable code identifying the failure; branch on this rather than on
message. One of bad_request, unauthorized, forbidden, not_found, conflict, service_unavailable, upstream_error, service_error, or internal_error.message?string
Human-readable explanation, safe to show to a user. For client errors it names the specific problem; for server-side failures it is a generic notice and the underlying detail is deliberately withheld.
404 · Index not found
error?string
Stable, machine-readable code identifying the failure; branch on this rather than on
message. One of bad_request, unauthorized, forbidden, not_found, conflict, service_unavailable, upstream_error, service_error, or internal_error.message?string
Human-readable explanation, safe to show to a user. For client errors it names the specific problem; for server-side failures it is a generic notice and the underlying detail is deliberately withheld.