Polymarket — Get a token's price history

Retrieve a token's price history with the Polymarket API. The sample response includes prices. Build a market research view or track changes over time. The GET request schema also lists token_id, start, end. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Outcome token id (the CLOB asset id the chart is keyed by). Required. `tokenId` is an accepted alias. This execution profile requires an explicit non-null value. The original optional/nullable OpenAPI declarations remain in officialOperation.
Optional parameters (7)
Window start, epoch seconds, INCLUSIVE. Alone it means "up to the present", and is capped at 15 days back from now. Pass `end` too when paging: a window that tracks the present keeps growing at the tip, and the 15-day cap is re-checked on every page, so a walk that starts near the cap can outlive it.
Window end, epoch seconds, EXCLUSIVE. Requires `start`; on its own it would ask for every point ever recorded up to `end`.
Relative window INSTEAD of `start`/`end`: `max`, `all`, `1m`, `1w`, `1d`, `6h`, `1h`, matched case-sensitively. An empty `interval=` is a malformed value, not an absent one. `max`/`all` serve the market's WHOLE life (back to 2022 for the oldest markets) at 12-hour buckets by default; at `bucket_seconds` of 10800 or 43200 the window is unbounded, while finer widths keep a 30-day window. The other intervals take a width sized to their own span when `bucket_seconds` is omitted (`1h`/`6h`/`1d` 60, `1w` 300, `1m` 1800), and each still floors an explicit value: 600 for `max`/`all`/`1m`, 300 for `1w`.
Bucket width in SECONDS (60…86400). `bucketSeconds` is an accepted alias. OMIT it and the server sizes the width to the window: the finest tier grain (60, 300, 1800, 10800, 43200) that keeps the series under ~2,500 points, except that an explicit window wider than 12 hours never defaults to the 60s grain (send `bucket_seconds=60` when you want second-by-minute detail over a longer window), and coarsened further if that grain no longer reaches the window's start. So a window up to 12 hours keeps 1-minute detail, half a day through a week defaults to 300, fifteen days to 1800; interval presets keep their own span-derived defaults (`1d` 60s, `1w` 300, `1m` 1800, and the unbounded `max`/`all` 43200). SEND it and it is served exactly as asked, which for a window older than that resolution's retention means an empty page rather than a silent substitution. An explicit value is also floored per interval: 600 for `max`/`all`/`1m`, 300 for `1w`.
Point-in-time read, epoch seconds, INCLUSIVE: the latest observation at or before this instant. Cannot be combined with a window. `asOf` is an accepted alias.
First-page size; defaults to the cap (10,000). Ignored when `cursor` is supplied (the cursor's size wins).
Opaque pagination cursor from a prior response's `next_cursor`.

Sample response

{
  "data": [
    {
      "price": 0.475,
      "resolution_seconds": 60,
      "timestamp": 1793196240
    },
    {
      "price": 0.475,
      "resolution_seconds": 60,
      "timestamp": 1793196300
    }
  ],
  "pagination": {
    "has_more": true,
    "limit": 2,
    "next_cursor": "eyJkYXRhIjp7InR5cGUiOiJwcmljZXNfaGlzdG9yeSIsInBhcmFtcyI6eyJsIjoyLCJ0cyI6MTc5MzE5NjMwMCwic3EiOiI2MCIsImQiOjJ9fSwic2lnIjoiYWRmNmQzMzBhN2Y3N2NjOTIyNDdkZjM2YjY4YzI3NjEifQ",
    "offset": 0
  }
}

Response result

Response structure

Inferred from examples
  • dataobject[]
    • pricenumber
    • resolution_secondsinteger
    • timestampinteger
  • paginationobject
    • has_moreboolean
    • limitinteger
    • next_cursorstring
    • offsetinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Polymarket — Get a token's price history with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.