Skip to main content
GET
cURL
Read this at client startup instead of hard-coding what the API covers. Polymarket is the only provider, so data.platforms has one key, polymarket, and every capability under it is supported today. For the list of routes, use API discovery.

Key response fields

Each of the 8 capabilities under data.platforms.polymarket takes one of three values: supported, partial, or unsupported. suspicious_trades and insider_radar name the same capability and always hold the same value. suspicious_trades is the current name; insider_radar stays for clients that already read it. Branch your client on the value, not on the key. Platforms says what each capability covers, and platform is polymarket on every V1 response that carries it.

Example

What it does not return

  • How Polymarket is doing right now. This matrix is fixed metadata and calls nothing at request time. Use Health to check that the API is up.
  • A partial or unsupported value today. Every Polymarket capability is supported, and the other two values exist so a client has something to branch on if that changes.
  • Routes or parameters. Those are in API discovery and the OpenAPI document.

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict

Response

Polymarket coverage

object
string
required
Allowed value: "platforms"
data
object
required
meta
object
required