Discover/Jewal Mart API
live

Jewal Mart APIjewalmart.in ↗

Get live INR gold and silver rates from Jewal Mart via one API endpoint. Returns 24K, 22K, 18K, and silver prices plus city-wise gold rate tables.

Endpoint health
verified 3h ago
get_gold_prices
1/1 passing latest checkself-healing
Endpoints
1
Updated
3h ago

What is the Jewal Mart API?

The Jewal Mart API exposes 1 endpoint — get_gold_prices — that returns up to 5 rate cards covering 24K, 22K, 18K gold and silver prices in INR, along with a city-wise breakdown of 24K, 22K, and 18K rates per gram. Each response includes the metal label, purity, unit, price, and displayed percentage change, making it straightforward to track Indian precious metal prices across multiple cities.

This call costs3 credits / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/1082e185-7a3a-4961-8188-98df7f03bba8/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/1082e185-7a3a-4961-8188-98df7f03bba8/get_gold_prices' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace jewalmart-in-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Jewal Mart gold & silver rates — current prices and city comparison."""
from parse_apis.jewalmart_in_api import JewalmartIn, ParseError

client = JewalmartIn()

# Fetch the current price report (all rate cards + city-wise table).
try:
    report = client.price_reports.get()
except ParseError as e:
    print(f"Could not retrieve prices: {e.code}")
    raise
print(f"Market: {report.market}  Currency: {report.currency}")

# Show each rate card — gold purities and silver.
if report.rates is not None:
    for rate in report.rates:
        purity_label = rate.purity if rate.purity else "N/A"
        print(f"  {rate.label} ({purity_label}): ₹{rate.price_inr}/{rate.unit}  change: {rate.change_pct}%")

# Compare 24K gold across cities.
for city_rate in report.city_rates:
    print(f"  {city_rate.city}: 24K ₹{city_rate.gold_24k_inr_per_gram}/g  22K ₹{city_rate.gold_22k_inr_per_gram}/g")

print("exercised: price_reports.get")
All endpoints · 1 totalmissing one? ·

Returns the rates shown on the site's Live Gold Prices page: one record per rate card (Gold 24K, 22K, 18K, 24K per 10 gram, Silver) with the INR price, unit and the displayed percentage change, and a city-wise table of 24K/22K/18K gold rates per gram. All prices are INR as published by the site (headline market: Chennai). The site publishes these values inside its page code and they change only when the site updates them; the response reflects whatever the page currently shows. No inputs. Two to three round trips per call. purity is null for the silver card. The city table is returned as published and may list a city more than once.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "rates": "array of rate cards: label, metal (gold|silver), purity (e.g. 24K, null for silver), price_inr (number), unit (gram or 10 gram), change_pct (displayed percentage change, number)",
    "market": "headline market the rate cards refer to (string)",
    "currency": "ISO currency code of all prices",
    "city_rates": "array of city rows: city, gold_24k_inr_per_gram, gold_22k_inr_per_gram, gold_18k_inr_per_gram (numbers)"
  },
  "sample": {
    "data": {
      "rates": [
        {
          "unit": "gram",
          "label": "Gold 24K",
          "metal": "gold",
          "purity": "24K",
          "price_inr": 15474,
          "change_pct": 0.15
        },
        {
          "unit": "gram",
          "label": "Silver",
          "metal": "silver",
          "purity": null,
          "price_inr": 249,
          "change_pct": 0.5
        }
      ],
      "market": "Chennai",
      "currency": "INR",
      "city_rates": [
        {
          "city": "Chennai",
          "gold_18k_inr_per_gram": 11606,
          "gold_22k_inr_per_gram": 14185,
          "gold_24k_inr_per_gram": 15474
        },
        {
          "city": "Mumbai",
          "gold_18k_inr_per_gram": 11640,
          "gold_22k_inr_per_gram": 14228,
          "gold_24k_inr_per_gram": 15520
        }
      ]
    },
    "status": "success"
  }
}

About the Jewal Mart API

What the API Returns

The get_gold_prices endpoint returns two main structures: a rates array and a city_rates array. The rates array contains one record per rate card published on Jewal Mart's Live Gold Prices page. Each record includes label, metal (either gold or silver), purity (e.g. 24K, 22K, 18K, or null for silver), price_inr as a number, unit (either gram or 10 gram), and a displayed percentage change field.

City-Wise Gold Rates

The city_rates array provides a row for each city listed on the page. Each row includes the city name and three numeric fields: gold_24k_inr_per_gram, gold_22k_inr_per_gram, and gold_18k_inr_per_gram. This makes it useful for applications that need to present or compare regional gold pricing within India without further computation.

Metadata Fields

The response also carries market — a string identifying the headline market the rate cards refer to — and currency, the ISO currency code (INR) confirming that all numeric prices are in Indian Rupees. The endpoint takes no input parameters; every call returns the full current snapshot of rates and city data as published on the source page.

Reliability & maintenanceVerified

The Jewal Mart API is a managed, monitored endpoint for jewalmart.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when jewalmart.in changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official jewalmart.in API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
3h ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display live 24K and 22K gold prices in INR inside a personal finance or investment tracking app.
  • Power a city-wise gold rate comparison tool showing 24K/22K/18K rates per gram across Indian cities.
  • Alert users when the displayed percentage change on gold or silver crosses a threshold.
  • Feed current silver and gold rates into a jewelry pricing calculator that converts gram-level costs.
  • Populate a dashboard that monitors Indian precious metal prices alongside other commodity data.
  • Log daily gold rate snapshots from the rates array for historical trend analysis over time.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Jewal Mart offer an official developer API?+
Jewal Mart (jewalmart.in) does not publish an official developer API or documented data feed. This Parse API is the structured way to access the rate data from that source.
What does the `rates` array contain versus the `city_rates` array?+
The rates array holds headline rate cards — one per metal/purity combination (24K, 22K, 18K gold, 24K per 10 gram, and silver) — each with a price, unit, purity, and percentage change. The city_rates array is a separate table with one row per city, containing only 24K, 22K, and 18K gold prices per gram with no percentage change field.
Does the API cover historical gold prices or just the current rate?+
The endpoint returns only the current rates as published on the page at the time of the call. Historical pricing data is not included. You can fork this API on Parse and revise it to add an endpoint that logs and retrieves historical snapshots.
Are silver city-wise rates available?+
Silver appears in the headline rates array with a price and percentage change, but the city_rates table covers only gold (24K, 22K, 18K). City-level silver rates are not currently exposed. You can fork this API on Parse and revise it to add city-wise silver data if that breakdown becomes available on the source page.
How fresh are the rates returned by this API?+
The API reflects whatever rates are currently displayed on the Jewal Mart Live Gold Prices page. Update frequency depends on how often Jewal Mart refreshes their published figures, which is not guaranteed to be real-time tick data. Treat the values as indicative daily or intraday rates rather than live exchange feed prices.
Page content last updated . Spec covers 1 endpoint from jewalmart.in.
Related APIs in FinanceSee all →