Understanding Matka Market Timings: A Complete Guide

If you are integrating matka results, the single most important concept to grasp is market timings. Each market declares results exactly twice a day — an open result and a close result — at fixed IST times. Knowing these times lets you schedule polling, predict when a market will go from "Pending" to "Open Declared" to "Complete", and pick the right markets for your audience.

The four sessions

Markets are grouped into four sessions:

| Session | Open window (IST) | Examples | |---|---|---| | Morning | 11:00 AM – 12:30 PM | Kalyan Morning, Milan Morning, Main Bazar Morning | | Day | 03:00 PM – 06:00 PM | Kalyan, Milan Day, Rajdhani Day, Main Bazar Day | | Evening | 07:30 PM – 09:30 PM | Sridevi Night, Supreme Day | | Night | 09:00 PM – 12:10 AM | Main Bazar, Kalyan Night, Milan Night, Rajdhani Night |

A market's session field in the API maps to one of these four. Use it to color-code your UI (e.g. morning markets in orange, night markets in indigo) — most matka result sites follow this convention.

Open vs Close — what you actually see

Each market has an openTime and a closeTime. Here is the typical lifecycle of a market over a day:

1. Pending (before openTime) — no result declared yet. Your board should show "Pending".
2. Open Declared (between openTime and closeTime) — the open pana has been published, the close pana has not. Your board shows the open pana + a placeholder for the jodi.
3. Complete (after closeTime) — both open and close declared. The full resultString (e.g. 456-56-123) is shown.

The API exposes this via the isComplete boolean on each result object. Use it to switch your UI state.

Starline markets — the exception

Starline markets (Kalyan Starline, Main Bazar Starline, Milan Starline, etc.) work differently. They declare results every hour on the hour from 11:00 AM through 10:00 PM. Each hourly slot is treated as a separate market — kalyan-starline-1100, kalyan-starline-1200, all the way through kalyan-starline-2200.

This means a single Starline provider publishes 12 results per day, not 2. Starline markets are extremely popular with mobile app users because of the high refresh frequency.

To list all Starline markets in the API:

curl -H "Authorization: Bearer $MATKA_API_KEY" \
     "https://sattamatkaapi.live/api/results/live?session=starline"

Teer markets — different game entirely

Shillong Teer, Khanapara Teer, Manipur Teer and friends operate on archery-based results — they publish two numbers called FR (first round) and SR (second round) at fixed afternoon/evening times. The API returns these in the same shape as regular matka results, with openPana representing the FR and closePana representing the SR.

How to look up timings for a specific market

Every market's timings are returned by the catalog endpoint:

curl -H "Authorization: Bearer $MATKA_API_KEY" \
     https://sattamatkaapi.live/api/markets/catalog

{
  "markets": [
    {
      "slug": "kalyan",
      "name": "Kalyan",
      "session": "day",
      "openTime": "03:45 PM",
      "closeTime": "05:45 PM",
      "active": true
    }
  ]
}

You can also visit /markets for a human-readable catalog with all 276+ markets and their timings, grouped by session.

Building a polling schedule

If you are polling the live board endpoint, you can save 60–70% of API calls by polling only when at least one market is in its active window. Here is a rough heuristic:

• 11:00 AM – 12:30 PM — morning markets + first Starline slot
• 02:45 PM – 06:00 PM — day markets + Starline afternoon slots
• 07:30 PM – 09:30 PM — evening markets + Starline evening slots
• 08:45 PM – 12:15 AM — night markets

Outside these windows, you can poll once every 5 minutes just to catch any late-declared close pana; inside the windows, poll every 30 seconds. Or — better — switch to webhooks and skip polling entirely.

Timezone gotchas

All times returned by the API are in Asia/Kolkata (IST, UTC+05:30). If your server runs in UTC, you need to convert. The result date field is also an IST date string like "2026-08-14", not a timestamp.

// Convert a "03:45 PM" IST time to a UTC Date for scheduling
function istToday(timeStr) {
  // Parse "03:45 PM" → 15:45
  const m = timeStr.match(/(\d+):(\d+)\s*(AM|PM)/)
  let hour = parseInt(m[1], 10) % 12
  if (m[3] === 'PM') hour += 12
  const now = new Date()
  // Build a UTC timestamp that represents this IST time
  return new Date(Date.UTC(now.getUTCFullYear(), now.getUTCMonth(), now.getUTCDate(), hour - 5, parseInt(m[2], 10) - 30))
}

Or just use the date-fns-tz package — it handles IST cleanly.

Summary

Knowing market timings is the difference between a results site that feels instant and one that lags by minutes. Use the catalog endpoint to discover every market's open/close times, group your UI by session, and pick a polling strategy that respects the windows above.