> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xinsider.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The Markdown of an API reference page leaves out the OpenAPI schema.
> Every object an endpoint returns or a webhook carries, with each field's type, presence and meaning, is on https://docs.0xinsider.com/api-reference/objects.md.
> The full OpenAPI 3.1 spec names each operation's and each webhook's exact parameters, request body and response schema: https://docs.0xinsider.com/api-reference/openapi.json.

# market_settled

> Sends a sports or esports game market's settlement once per settled state: the game, its league, the market type, the outcome names, and the payouts.

Each delivery is one settled state of one game market, usually within a few minutes of Polymarket resolving it. A market can settle twice: first as a resolved oracle question without payouts, then with them. Each state is sent once, with its own `settlement_id`. Pro and Max only.

Subscribe with `settlement_filters` on [create](https://docs.0xinsider.com/api-reference/endpoint/create-webhook.md) or update to choose the markets: `leagues` (at most 32), `sports_market_types` (at most 64; `*` is every type), `event_slugs` (at most 100), and `condition_ids` (at most 100). Every field you set must match.

Without `sports_market_types`, an endpoint receives the markets Polymarket labels `moneyline`, or every type of the markets `condition_ids` names. Most markets that settle are props, spreads, and totals: name their types, or send `["*"]`, to receive them.

The `moneyline` label is each head-to-head game's winner market. In golf and other field events, Polymarket labels every player market `moneyline`: the winner, make the cut, and round leader markets. One tournament can send hundreds of states. On November 7, 2026, one golf tournament sent 452 states to an endpoint with the default filter in about two minutes.

To leave those out, set `leagues` to the leagues you want, or name markets with `condition_ids`. A market's `league` is the first part of its event slug. A golf event slug that starts with a year, such as `2026-world-wide-technology-championship`, has a `null` league, and no `leagues` list matches it.

`settlement` is the same object [`GET /api/v1/games/{event_slug}/markets`](https://docs.0xinsider.com/api-reference/endpoint/list-game-markets) serves: `payouts` per share in micro-USDC in outcome order, `result` (`outcome` or `split`), `winning_outcome_index`, `was_disputed`, `resolved_at`, and `observed_at`, when we first saw this state. `outcomes` holds each outcome name at its index, so `outcomes[winning_outcome_index]` names the winner.

A Polymarket `polyv2` copy of a game carries `copy_of_event_slug`, the original game's slug. It is sent only to a filter that names its condition ID or its own event slug, so a league subscription does not receive the same game twice. A state we first see more than 6 hours after it resolved is not sent.

The [OpenAPI spec](https://docs.0xinsider.com/api-reference/openapi.json) carries an example delivery, `epl_moneyline_settled`, that you can sign and post to your own server to test it. The `MarketSettled` frame on [Stream](https://docs.0xinsider.com/api-reference/endpoint/get-stream.md) carries the same fields for every game market, without `settlement_filters`. The [Webhooks guide](https://docs.0xinsider.com/guides/webhooks.md) covers signatures, retries, and replay.


## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.0xinsider.com/llms.txt).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.