How to Read an Event Page Versus a Market Page

A market is the thing you can trade: one binary Yes/No question, with one Yes token and one No token. An event is a container that groups one or more of those markets under a shared question set. The headline on the screen is a title. It is not, by itself, the book.

This page is about that split, on documented public pages retrieved 2026-08-16T00:50Z. It is not a rewrite of the already-live negative-risk guide. That companion owns the conversion that can turn one No into a Yes on every other named outcome. This page owns the container versus the book, and the documented URL paths that tell you which one you opened.

What this page does not claim. It does not describe the current buttons, tabs, or layout of the public website — those were not screenshotted tonight. It does not treat a documentation illustration as a live 2026 book. It does not say a live book sums to a dollar. It does not tell you to trade the named outcome, to convert a No, or to treat an event-page screenshot as a fill.

A market is the Yes/No book

The Markets & Events page calls a market "the fundamental tradable unit." Each market is a single binary question with Yes and No outcomes. The same page lists three identifiers on every market: a Condition ID for the conditional-token contract, a Question ID used for resolution, and ERC-1155 token IDs — one for Yes, one for No.

The Positions & Tokens page says the same thing in payoff language. Each market has exactly two outcome tokens. Yes redeems $1.00 if the described thing occurs. No redeems $1.00 if it does not. Every Yes/No pair in existence is backed by exactly $1 of pUSD collateral locked in the conditional-token contract. How those two prices should add up to about a dollar is a separate companion. This page only needs the pair, so it has something to contrast with a container.

The vendor's own market example on that Markets & Events page is the question "Will Bitcoin reach $150,000 by December 2026?" Yes redeems $1 if Bitcoin reaches $150k; No redeems $1 if it does not. That is a documentation illustration retrieved 2026-08-16T00:50Z. It is not a live book and not a price.

A market can exist without a book you can trade. Official docs say markets can be traded on the CLOB only if enableOrderBook is true, and that some markets exist onchain without order-book trading. Market Details adds that a market may exist before its order book opens and remain discoverable after it closes. Existence of a page is not a fill.

An event is a container

The same Markets & Events page defines an event as a container that groups one or more related markets. Discover Markets says it in one sentence: an event groups one or more markets under a shared question set. A single-market event asks one yes/no question. A multi-market event splits a broader question into individual outcomes — the page's example is one market per candidate in an election.

The market-data overview is blunt about where the book lives. Each market is a tradable question with YES and NO outcomes. Each outcome has its own token ID. The token ID is what you use to read a price or an order book. The event is how those markets are grouped. The book is not the group.

How the URL tells you which object you opened

Official docs publish both URL shapes.

An event is addressed as https://polymarket.com/event/{slug}. The Markets & Events page's own example is https://polymarket.com/event/fed-decision-in-october, slug fed-decision-in-october. Discover Markets fetches an event from a URL of the same shape.

A market is addressed as https://polymarket.com/market/{slug}. Discover Markets fetches a market from https://polymarket.com/market/will-the-us-confirm-that-aliens-exist-before-2027-789-924-249. Market Details says the market slug is for fetching a known market "or linking to its human-readable page."

That is the documented reader check. Look at the path. /event/ is the container. /market/ is the book. This page does not claim that every link a person actually lands on tonight uses those paths. It claims that those are the paths the vendor published.

Same headline, different slugs

A matching title is not identity of the object. Discover Markets' own event example — documentation, not a live census — gives event id 90177 the slug will-the-us-confirm-that-aliens-exist-before-2027 and the title "Will the US confirm that aliens exist by...?". Nested under it is market id 703257, slug will-the-us-confirm-that-aliens-exist-before-2027-789-924-249, question "Will the US confirm that aliens exist before 2027?". The event slug and the market slug are not the same string. The market URL uses /market/ plus the longer slug.

On a single-market event the Markets & Events page says the event and the market are "essentially equivalent." That is vendor wording about the question, not a claim that the identifiers match. The same page's single-market tree uses a Bitcoin-to-$100,000-by-December-2024 illustration, which is a different wording from the $150,000-by-December-2026 market example a few paragraphs above. Both are documentation. Neither is a live 2026 book.

Several books under one headline

When an event contains two or more markets, official docs say it groups related binary questions. Some of those groups are mutually exclusive. The Markets & Events page says Polymarket links those mutually exclusive markets as a negative-risk group: exactly one market in the group resolves Yes, and every other market resolves No. The page's illustration is a 2024 Presidential Election event with separate Yes/No markets for Donald Trump, Joe Biden, Kamala Harris, and Other.

That is a container holding several books. It is not one four-way token. Each name is still a market with its own Yes and its own No. Whether those books are independent or linked by a conversion is a different question. The already-live negative-risk guide owns the conversion. Market Details notes that negRisk is a market-level flag, and that augmented negative risk is configured on the event. This page stops there.

A third layer, named so it is not mistaken for one book

Discover Markets also defines a series: a recurring set of events under one theme — a weekly Fed-decision series with one event per meeting, or a season-long league series with one event per matchup. The documentation example is series id 1, slug nfl, title NFL, recurrence weekly.

For sports, the same page says a game's markets can be split across a main event and companion events. Companion slugs extend the main event's slug with a suffix such as -player-props, -halftime-result, or -more-markets. The illustration uses mls-chi-vwh-2026-07-16 plus those suffixes. That date is in the documentation slug. It is not a live card, and this page is not a sports primer. The only use of the example is the structure: one game, several events, each event still a container of markets.

A reading routine

Read the path before the headline. /event/ is a container. /market/ is a book. If the path is /event/, ask how many markets the docs say that kind of event can hold — one, or several. If several, each name is still a Yes/No market with its own token IDs. The token ID, not the event title, is what official docs say you use to read a book. A market can exist without enableOrderBook. A page can exist after the book has closed.

Then stop. This page does not tell you to trade either object. It does not treat the headline as the contract. The contract rules, the resolution source, and the deadline still have to be read on the market you actually mean — and those are other guides.