API + MCP live · talk to us

// GLOSSARY

Condition ID

Polymarket's onchain identifier for a market's resolution condition — a 0x-prefixed hash from the conditional tokens framework. Each market has one condition ID; each outcome within it has its own token ID. The key you join metadata and orders on.

Every Polymarket market is anchored to a condition — the onchain object that will eventually resolve yes or no. Its identifier, the condition ID, is a 32-byte hash (rendered as a long 0x string) derived under the conditional tokens framework.

How the IDs relate

  • Condition ID — the market ("Will X happen?"). One per market.
  • Token ID — one per outcome (yes and no), the ERC-1155 asset you actually trade on the CLOB.
  • Slug / question ID — human-readable handles in the Gamma API metadata.

A common integration bug is joining on the wrong one: order placement wants token IDs, while much of the metadata is keyed by condition ID or slug.

Contrast with Kalshi

Kalshi uses human-readable tickers (market, event, and series levels) instead of hashes. Mapping a Kalshi ticker to the equivalent Polymarket condition is exactly the problem a unified market ID solves — see unified market IDs.