Skip to main content
GET
/
api
/
v1
/
polymarket
/
market
/
date-range
Get Polymarket Market Date Range
curl --request GET \
  --url https://api.entityml.com/api/v1/polymarket/market/date-range \
  --header 'Authorization: <authorization>'
{
  "market_condition_id": "<string>",
  "has_data": true,
  "start_date": "<string>",
  "end_date": "<string>",
  "available_date_count": 123
}

​
Request

​
Headers

​
Authorization
string
required
Bearer token. Example: Bearer YOUR_API_KEY

​
Query Parameters

​
condition_id
string
required
The Polymarket market condition ID. Values are accepted with or without the 0x prefix.

​
Response

​
market_condition_id
string
The normalized Polymarket market condition ID.
​
has_data
boolean
Whether any stored data was found for the market.
​
start_date
string
Earliest stored date for this market, or null if none exists.
​
end_date
string
Latest stored date for this market, or null if none exists.
​
available_date_count
integer
Number of distinct stored dates found for the market.
Use this endpoint as the authoritative per-market availability check before requesting raw Polymarket data. Orderbook data exists for a subset of Polymarket markets from 2025-09-01, but coverage is not continuous. Continuous Polymarket crypto-related market coverage begins on 2026-02-04, and continuous coverage for all Polymarket markets begins on 2026-04-02.
GET /api/v1/polymarket/market/date-range reflects stored dates in S3. It does not prove every second in that day is complete. GET /api/v1/polymarket/market/data still rejects dates earlier than 2026-02-08.

​
Example

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.entityml.com/api/v1/polymarket/market/date-range?condition_id=8213d395e079614d6c4d7f4cbb9be9337ab51648a21cc2a334ae8f1966d164b4"

​
Example response

{
  "market_condition_id": "0x8213d395e079614d6c4d7f4cbb9be9337ab51648a21cc2a334ae8f1966d164b4",
  "has_data": true,
  "start_date": "2026-02-04",
  "end_date": "2026-02-14",
  "available_date_count": 8
}