Endpoint Playground

Try the Kalshi Historical Cutoff API

Returns the three cutoff timestamps Kalshi uses to split live from historical data: `market_settled_at`, `orders_updated_at` and `trades_created_at`. Use them to decide when settled market data should be read from the historical endpoints. Takes no parameters.

What a live request returned

14 Oct 2026: Single record response; 3 fields had a value in every checked item.

Observed request: GET /kalshi/historical/cutoff
Fields with a value in every checked item: market_settled_at, orders_updated_at, trades_created_at

Sample value profiles: market_settled_at: 2026-08-14; orders_updated_at: 2026-09-29; trades_created_at: 2026-08-14.

Request: GET /kalshi/historical/cutoff
Cost: 1 credit/request
Auth: apiKey
Checks passed, 7 days to 14 Oct 2026: 100%, median 0.16 s
Monitored request: GET /kalshi/historical/cutoff

Kalshi Historical Cutoff API documentation Kalshi platform page Pricing

Prefilled cURL

curl 'https://api.crawlora.net/api/v1/kalshi/historical/cutoff' \
  -H "x-api-key: $CRAWLORA_API_KEY"

Request parameters

No request parameters

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "market_settled_at": "2026-04-08T00:00:00Z",
    "orders_updated_at": "2026-04-08T00:00:00Z",
    "trades_created_at": "2026-04-08T00:00:00Z"
  }
}

More Kalshi endpoints

Kalshi event detail Kalshi event history Kalshi event metadata Kalshi events Kalshi multivariate events Kalshi exchange schedule Kalshi exchange status Kalshi historical market detail Kalshi historical market history Kalshi historical markets Kalshi historical trades Kalshi market detail All 21 Kalshi endpoints

The sample response, schema and code snippets below work without an account. Sending a live request needs an API key.

Set up API key Endpoint docs

Endpoint

Choose one catalog endpoint for this request.

1 shown

Group

Method

Auth

Endpoint

GETapiKey1 credit/requestkalshi.historicalCutoffResponseDocKalshi

GET /kalshi/historical/cutoff

Kalshi historical data cutoff

Response behavior

- This endpoint is a discovery utility for deciding when settled market data should be read from historical endpoints.

API key required. Paste a full key or rotate one from the API Keys page.

Set up API key

View docs

API key

API key required for live requests. Your key is only used to send requests from this Playground.

not configured

Active Playground key: not configured

Manage API keys in Console

Add an API key to send a live request.

If an active API key is configured, Copy cURL includes it. Share links never include API keys.

View docs

Sample responseGET

Shown before your first request. Add an API key and send a request to see the live response, status, latency, and headers.

{
  "code": 200,
  "msg": "OK",
  "data": {
    "market_settled_at": "2026-04-08T00:00:00Z",
    "orders_updated_at": "2026-04-08T00:00:00Z",
    "trades_created_at": "2026-04-08T00:00:00Z"
  }
}

Endpoint Playground

Try the Kalshi Historical Cutoff API

What a live request returned

14 Oct 2026: Single record response; 3 fields had a value in every checked item.

Observed request: GET /kalshi/historical/cutoff
Fields with a value in every checked item: market_settled_at, orders_updated_at, trades_created_at

Sample value profiles: market_settled_at: 2026-08-14; orders_updated_at: 2026-09-29; trades_created_at: 2026-08-14.

Request: GET /kalshi/historical/cutoff
Cost: 1 credit/request
Auth: apiKey
Checks passed, 7 days to 14 Oct 2026: 100%, median 0.16 s
Monitored request: GET /kalshi/historical/cutoff

Kalshi Historical Cutoff API documentation Kalshi platform page Pricing

Prefilled cURL

curl 'https://api.crawlora.net/api/v1/kalshi/historical/cutoff' \
  -H "x-api-key: $CRAWLORA_API_KEY"

Request parameters

No request parameters

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "market_settled_at": "2026-04-08T00:00:00Z",
    "orders_updated_at": "2026-04-08T00:00:00Z",
    "trades_created_at": "2026-04-08T00:00:00Z"
  }
}

More Kalshi endpoints

The sample response, schema and code snippets below work without an account. Sending a live request needs an API key.

Set up API key Endpoint docs

Endpoint

Choose one catalog endpoint for this request.

1 shown

Group

Method

Auth

Endpoint

GETapiKey1 credit/requestkalshi.historicalCutoffResponseDocKalshi

GET /kalshi/historical/cutoff

Kalshi historical data cutoff

Response behavior

- This endpoint is a discovery utility for deciding when settled market data should be read from historical endpoints.

API key required. Paste a full key or rotate one from the API Keys page.

Set up API key

View docs

API key

API key required for live requests. Your key is only used to send requests from this Playground.

not configured

Active Playground key: not configured

Manage API keys in Console

Add an API key to send a live request.

If an active API key is configured, Copy cURL includes it. Share links never include API keys.

View docs

Sample responseGET

Shown before your first request. Add an API key and send a request to see the live response, status, latency, and headers.

{
  "code": 200,
  "msg": "OK",
  "data": {
    "market_settled_at": "2026-04-08T00:00:00Z",
    "orders_updated_at": "2026-04-08T00:00:00Z",
    "trades_created_at": "2026-04-08T00:00:00Z"
  }
}