Ponn.in

Free Kerala Gold Rate API

One JSON file with today's 18K, 22K and 24K gold rates in Kerala, per gram and per pavan. No key. No sign-up. No request limit from us.

Endpoint

GET, no key neededhttps://ponn.in/kerala_gold_rate_today.json

Free for any developer, in personal and commercial projects. No API key, no sign-up and no request limit set by us.

Quick start

# A plain GET. No API key and no headers.
curl -fsS https://ponn.in/kerala_gold_rate_today.json
// A plain GET: do not add custom headers (they trigger a preflight, which is not supported).
const res = await fetch("https://ponn.in/kerala_gold_rate_today.json");
if (!res.ok) throw new Error("HTTP " + res.status); // keep your last good value
const d = await res.json();

const { per_gram, per_pavan } = d.rates.k22;
console.log(per_gram, per_pavan); // 12215 97720
console.log(d.rate_date, d.updated_at); // check how fresh it is

The response

{
  "schema_version": 1,
  "currency": "INR",
  "region": "Kerala",
  "timezone": "Asia/Kolkata",
  "grams_per_pavan": 8,
  "rate_date": "2026-11-18",
  "updated_at": "2026-11-18T10:40:39+05:30",
  "rates": {
    "k22": {
      "per_gram": 12215,
      "per_pavan": 97720
    },
    "k24": {
      "per_gram": 13331,
      "per_pavan": 106648
    },
    "k18": {
      "per_gram": 10000,
      "per_pavan": 80000
    }
  }
}

Fields

Every field is always present and is never null. Amounts are JSON integers in whole rupees.

FieldTypeMeaningExample
schema_versionintegerThe version of the file shape. Always 1 in kerala_gold_rate_today.json. A breaking change would be a new file name, never a new number here.Example: 1
currencystringCurrency of every amount. Always "INR". All amounts are whole rupees.Example: "INR"
regionstringThe market the rates are for. Always "Kerala" in this file.Example: "Kerala"
timezonestringThe time zone behind rate_date and updated_at. Always "Asia/Kolkata" (UTC+05:30, no daylight saving).Example: "Asia/Kolkata"
grams_per_pavanintegerGrams in one pavan. Always 8. It is the unit behind every per_pavan value.Example: 8
rate_datestring, YYYY-MM-DDThe Indian date the rate applies to. It can be earlier than today, for example before the first update of a new day.Example: "2026-11-18"
updated_atstring, date and timeWhen the rate was last updated, in Indian time. Always the form YYYY-MM-DDTHH:MM:SS+05:30, whole seconds. This is the only freshness signal, and it matches "Last updated" at the bottom of every page.Example: "2026-11-18T10:40:39+05:30"
ratesobjectRates by purity. Exactly three keys: k22, k24 and k18. Always look a rate up by key, never by position.Example: { "k22": {...}, "k24": {...}, "k18": {...} }
rates.k22.per_gramintegerRupees for 1 gram of 22K (916) gold. Whole rupees, above zero.Example: 12215
rates.k22.per_pavanintegerRupees for 1 pavan (8 g) of 22K gold, as published. Use it as it is.Example: 97720
rates.k24.per_gramintegerRupees for 1 gram of 24K (999) gold.Example: 13331
rates.k24.per_pavanintegerRupees for 1 pavan of 24K gold, as published.Example: 106648
rates.k18.per_gramintegerRupees for 1 gram of 18K (750) gold.Example: 10000
rates.k18.per_pavanintegerRupees for 1 pavan of 18K gold, as published.Example: 80000

Purity: 24K is 999 fine gold, 22K is 916 (the usual hallmark) and 18K is 750. The rates are indicative reference rates and exclude GST, making charges and other shop costs.

Freshness and caching

  1. The file changes only when a new rate is recorded, usually a few times a day. An old updated_at is normal, not an error.
  2. rate_date is the Indian date the rate applies to and updated_at is when it was last updated. Do not work one out from the other. Both use Indian time (+05:30).
  3. Keep a copy for a minute or more. For a live display, check every 5 to 15 minutes. For a calculator, once per page load or once an hour is plenty. The server sends an ETag, so an unchanged file answers with a short 304.
  4. Handle failures by keeping your last good value. If the status is not 200, or the body is not valid JSON, keep what you had. A wrong path returns 404.

Send a plain GET or HEAD with no query and no custom headers. OPTIONS and preflight requests are not supported.

More examples

Python

import requests
from datetime import datetime

r = requests.get("https://ponn.in/kerala_gold_rate_today.json", timeout=10)  # plain GET, no headers
r.raise_for_status()                 # not 200: keep your last good value
d = r.json()

k22 = d["rates"]["k22"]
print(k22["per_gram"], k22["per_pavan"])        # 12215 97720
print(datetime.fromisoformat(d["updated_at"]))  # 2026-11-18 10:40:39+05:30

PHP

<?php
$ctx = stream_context_create(['http' => ['timeout' => 10]]);
$body = file_get_contents('https://ponn.in/kerala_gold_rate_today.json', false, $ctx);
if ($body === false) { exit("Fetch failed: keep your last good value\n"); }
$d = json_decode($body, true, 512, JSON_THROW_ON_ERROR);

$k22 = $d['rates']['k22'];
echo $k22['per_gram'], ' ', $k22['per_pavan'], "\n";   // 12215 97720
echo (new DateTime($d['updated_at']))->format('c'), "\n";

jq on the command line

curl -fsS https://ponn.in/kerala_gold_rate_today.json | jq -r '"22K: Rs \(.rates.k22.per_gram) per gram, Rs \(.rates.k22.per_pavan) per pavan (updated \(.updated_at))"'

# One row per purity: key, per gram, per pavan
curl -fsS https://ponn.in/kerala_gold_rate_today.json | jq -r '.rates | to_entries[] | [.key, .value.per_gram, .value.per_pavan] | @csv'

Stability promise

  1. These stay as they are: the path /kerala_gold_rate_today.json, every key name, every type, whole-rupee integers, the date and time formats, and what each value means.
  2. New keys may be added later. Keys are never removed, renamed or changed in type. Ignore keys you do not know, and do not reject a file for having extra keys.
  3. A breaking change would be a new file such as kerala_gold_rate_today_v2.json, published next to this one. Version 1 would keep working for at least 12 months after that.
  4. Look rates up by key (rates.k22), never by position or order.

A JSON Schema for version 1 is at /kerala_gold_rate_today.schema.json.

Terms of use

Free to use, including in commercial projects. A link back to Ponn.in is appreciated but not required. The rates are indicative reference rates for information only: not an offer to buy or sell and not a settlement price. The service is provided as it is, with no warranty and no uptime guarantee, and it may be changed or withdrawn. Read the disclaimer.

Changelog

17 Nov 2026: Version 1 launched.

Questions

Is it really free?

Yes. There is no API key and no sign-up, and Ponn.in sets no request limit. It is free for personal and commercial projects. A link back to Ponn.in is welcome but not required.

Is there a rate limit?

We do not set one. The file is a static file served from a global network and it changes only a few times a day, so please keep a copy for a minute or more instead of fetching it on every page view. The service is provided as it is, with no uptime guarantee, and may be changed or withdrawn.

How often does it change?

Only when a new rate is recorded, usually a few times a day. On a quiet day the file stays the same for hours, and an old updated_at is normal.

Why is updated_at hours old?

Because the rate has not been updated since then. Compare rate_date with today's Indian date to see whether you have the latest day, and treat the file as stale if you need fresher data than it offers.

Why does my browser show a CORS error?

Any website can read the file with a plain GET. If you add custom request headers, such as Authorization or X-API-Key, the browser sends a preflight request first, and a static file cannot answer it. Remove the custom headers.

Are these the price I pay at a shop?

No. They are indicative reference rates per gram and per pavan. A shop price adds making charges, GST and other costs, and may differ. See the disclaimer.

Related