API Documentation

Everything you need to integrate live Kolkata FF and Matka results into your application.

Getting Started Authentication Kolkata FF Endpoints Matka Endpoints Errors Rate Limits

Getting Started

Every request needs an API key and secret, issued per module (Kolkata FF or Matka API) with a chosen plan duration. Get in touch to have one created for you, then use the key/secret pair below to sign your requests.

Base URL: https://jadumatkaapi.com

Authentication

Every request must include three headers. The signature is an HMAC-SHA256 hash of the current unix timestamp, keyed with your secret key. The timestamp must be within 5 minutes of the server time.

Header Value
X-API-KEY Your API key (token)
X-Timestamp Current unix timestamp (seconds)
X-Signature HMAC-SHA256(timestamp, secret_key)
TOKEN="YOUR_API_KEY"
SECRET="YOUR_SECRET_KEY"
TS=$(date +%s)
SIG=$(echo -n "$TS" | openssl dgst -sha256 -hmac "$SECRET" | sed 's/^.* //')

curl "https://jadumatkaapi.com/api/v1/matka/markets-result" \
  -H "X-API-KEY: $TOKEN" \
  -H "X-Timestamp: $TS" \
  -H "X-Signature: $SIG"

Kolkata FF Endpoints

Requires an active Kolkata FF subscription.

GET /api/v1/kolkata/live

Returns the currently live (or most recently declared) baji result.

Example Response

{
  "status": 200,
  "live_time": "10:03 am",
  "baji_type": 1,
  "result_holiday": "no",
  "data": {
    "patti": "245",
    "ank": "1",
    "date": "2026-08-09"
  }
}
GET /api/v1/kolkata/today-result

Returns all 8 baji slots for today, with status DECLARED, LIVE or UPCOMING.

Example Response

{
  "status": 200,
  "data": [
    {
      "baji_type": 1,
      "time": "10:00 am",
      "patti": "245",
      "ank": "1",
      "date": "2026-08-09",
      "status": "DECLARED"
    },
    {
      "baji_type": 2,
      "time": "11:00 am",
      "patti": null,
      "ank": null,
      "date": "2026-08-09",
      "status": "UPCOMING"
    }
  ]
}

Matka API Endpoints

Requires an active Matka API subscription.

GET /api/v1/matka/markets-result

Returns all active markets with today's result (if declared).

Query Parameters

Param Type Description
slug string Optional. Comma-separated market slugs to filter, e.g. kalyan,milan-morning

Example Response

{
  "success": true,
  "message": "Markets fetched successfully",
  "count": 1,
  "data": [
    {
      "id": 1,
      "market_name": "kalyan",
      "slug": "kalyan",
      "openh": "05",
      "openm": "25",
      "openap": "pm",
      "closeh": "06",
      "closem": "25",
      "closeap": "pm",
      "sat": "yes",
      "sun": "no",
      "today_result": {
        "open": "137",
        "jodi": "18",
        "close": "477"
      }
    }
  ]
}

Error Responses

Status Message Meaning
401 Missing authentication headers One of the 3 required headers wasn't sent
401 Invalid API key The key doesn't exist
401 Request expired Timestamp is more than 5 minutes off
403 Invalid signature Signature doesn't match the timestamp + secret
403 Account inactive or blocked Your account status isn't active
402 Subscription expired Renew your plan to keep using the API
403 API key not subscribed to this module This key is for a different module (Kolkata FF vs Matka API)
429 API usage limit exceeded Monthly request limit reached for this key

Rate Limits

Each API key has a monthly request allowance based on your plan. There's no fixed per-second limit, but sustained heavy traffic beyond your plan's usage limit will start returning 429 until the next billing cycle. See pricing for plan details.