Get Kerala Gold 24k (KERA-24k) prices from various markets using this API

If your goal is to deliver Kerala Gold 24k (KERA-24k) pricing from multiple markets into your app, ERP, or pricing engine, you can do it reliably with the Metals-API JSON REST API. In practice, there is no separate “KERA-24k” symbol: you derive a Kerala-grade 24k quote starting from Gold (XAU) per troy ounce, then express it in Indian Rupees (INR), optionally convert to grams, and, if needed, add local market premiums or fees. This article shows how to build that pipeline end-to-end using Metals-API’s latest, historical, time-series, bid/ask, OHLC, fluctuation, convert, and carat features, with attention to units, base currency, timestamps, and operational best practices.

What “Kerala Gold 24k (KERA-24k)” Means Technically

Traders and jewelers in Kerala often refer to “24k gold price” as a local benchmark for retail or wholesale transactions. From a data-integration perspective, this benchmark can be modeled as:

A global reference: Gold (XAU), quoted per troy ounce.
A local currency expression: INR as base currency.
A purity-adjusted view: 24k carat (pure gold), aligned with XAU’s purity baseline.
Optional regional adjustments: local making charges, taxes, logistics, or bid/ask-induced premiums.

Metals-API delivers XAU rates in a simple JSON format that you can convert into INR and per-gram values instantly. You can then apply any Kerala-specific uplift or fees downstream based on your business logic. Start by reviewing the Metals-API Supported Symbols and the Gold symbol (XAU), then use INR as your base in requests where appropriate.

Core Concepts You’ll Use to Price Kerala 24k Gold

Units: Metals are quoted per troy ounce (31.1034768 grams). You’ll usually convert XAU/INR per oz to INR/gram for retail quoting.
Base currency: By default, Metals-API responses are relative to USD. You can set base=INR where supported to avoid an extra conversion step, or use the convert endpoint.
Purity: 24k is essentially pure gold. If you must express 22k, 18k, etc., you can scale by purity or use the carat endpoint where available.
Market structure: Kerala market quotes may reflect local bid/ask spreads, making charges, and taxes. Use bid/ask for tight spreads and add your internal markups after computing a clean INR/gram price.
Trading hours and weekends: Metals trade continuously on OTC and exchange venues, but liquidity varies. Expect lower update frequency or flat lines during weekends and public holidays.

How Metals-API Fits: Real-Time and Historical Gold Data

Metals-API provides a reliable backbone for pricing, charting, and analytics:

Latest Rates: Real-time XAU quotes updated according to plan tier; your app can refresh at your target frequency.
Bid/Ask: Granular spreads to anchor risk-aware quotes and hedging logic.
OHLC: Open/High/Low/Close for daily chart data and technical analysis.
Time Series: Backfill charts and train models across a date range.
Fluctuation: Get daily change and percentage movement for alerts and summaries.
Historical: Snapshot from a specific date—ideal for valuation and P&L look-backs.
Convert: Convert USD↔XAU↔INR or oz↔grams workflows via your app logic.
Carat: Retrieve gold rates by carat if you need purity-based quoting beyond 24k.

Explore the endpoints and parameters in the Metals-API Documentation, and get started quickly from the Metals-API Website. If you don’t yet have credentials, sign up now to get your free API key and start prototyping.

Architecting a Kerala 24k Pricing Flow

A typical “KERA-24k” workflow looks like this:

Fetch XAU rates (latest or intraday as needed). Where supported, request base=INR to get INR-denominated prices directly.
Compute INR per gram: INR_per_gram = (INR per troy ounce) / 31.1034768.
Apply any local adjustments: making charges, GST, logistics, and a margin. Keep base values for transparency in your UI.
Optionally, use Bid/Ask prices to produce buy/sell quotes with clearly defined spreads.
Persist time-series and OHLC data to power charts and analytics in your product.
Build alerting on top of fluctuation data for daily movements or thresholds.

This setup keeps the global reference intact while still delivering user-facing Kerala pricing. For other regions, reuse the same architecture with different base currencies or premiums.

Requesting Latest XAU Rates: cURL and JSON Walkthrough

Below is a representative JSON response for latest rates, returned per troy ounce relative to a base currency. You can pass access_key, symbols (e.g., XAU), and optionally base=INR depending on your plan. The response structure mirrors the real payload your app will consume. Then we’ll break down the fields relevant to Kerala pricing.

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": 0.000482,
"XAG": 0.03815,
"XPT": 0.000912,
"XPD": 0.000744,
"XCU": 0.294118,
"XAL": 0.434783,
"XNI": 0.142857,
"XZN": 0.344828
},
"unit": "per troy ounce"
}

Field notes for Kerala pricing:

success: Boolean indicating request success.
timestamp: Unix time for the data point. Always store and display in UTC internally; convert to IST for UI if needed.
base: If set to USD, the XAU value reflects ounces of gold you’d get per USD. In many flows, you’ll invert this to compute the USD price per ounce, or simply request base=INR to get INR directly.
rates.XAU: The core gold rate. Use this in your conversion to INR/gram.
unit: Always “per troy ounce” for metals. Remember 1 troy ounce = 31.1034768 grams.

Example cURL request to get latest XAU with INR base (adjust to your plan parameters):

curl -G https://api.metals-api.com/latest \
--data-urlencode "access_key=YOUR_API_KEY" \
--data-urlencode "base=INR" \
--data-urlencode "symbols=XAU"

If your plan doesn’t allow base=INR, request USD and either:

Make a second call to get USD/INR from the same API (if supported), then convert locally, or
Use the convert endpoint to go directly from USD to XAU or from XAU to INR as needed.

JavaScript Example: Compute Kerala 24k INR/gram from XAU

The following JavaScript snippet demonstrates fetching the latest XAU rate and deriving INR per gram suitable for a Kerala 24k display. It also shows how to handle timestamps and caching basics.

// Basic example; add robust error handling and retry logic in production.
async function fetchKerala24kInrPerGram() {
const API_URL = "https://api.metals-api.com/latest";
const params = new URLSearchParams({
access_key: "YOUR_API_KEY",
base: "INR",
symbols: "XAU"
});

// Simple client-side cache key
const cacheKey = "kerala24k_inrgram_cache";
const cached = localStorage.getItem(cacheKey);
if (cached) {
const { timestamp, value } = JSON.parse(cached);
// Cache for up to 60 seconds (tune to your plan's data update frequency)
if (Date.now() - timestamp < 60000) {
return value;
}
}

const res = await fetch(`${API_URL}?${params.toString()}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.json();
if (!data.success || !data.rates || !data.rates.XAU) {
throw new Error("Invalid Metals-API response");
}

// data.rates.XAU is XAU per INR (depending on base). Confirm semantics based on your plan.
// Convert INR per troy ounce to INR per gram:
// If 'base=INR' returns XAU per INR, invert for INR per XAU:
const xauPerInr = data.rates.XAU;
const inrPerXau = 1 / xauPerInr;
const TROY_OZ_TO_GRAMS = 31.1034768;
const inrPerGram = inrPerXau / TROY_OZ_TO_GRAMS;

// Optionally add local adjustments (example: 3% premium)
const keralaAdjustmentPct = 0.03;
const finalKeralaInrPerGram = inrPerGram * (1 + keralaAdjustmentPct);

localStorage.setItem(cacheKey, JSON.stringify({
timestamp: Date.now(),
value: {
inrPerGramBase: inrPerGram,
inrPerGramKerala: finalKeralaInrPerGram,
sourceTimestamp: data.timestamp,
base: data.base,
unit: "INR/gram"
}
}));

return {
inrPerGramBase: inrPerGram,
inrPerGramKerala: finalKeralaInrPerGram,
sourceTimestamp: data.timestamp,
base: data.base,
unit: "INR/gram"
};
}

// Usage:
// fetchKerala24kInrPerGram().then(console.log).catch(console.error);

Implementation notes:

Base currency direction: Always verify whether rates.XAU is “XAU per INR” or “INR per XAU” according to your chosen base and plan. If it is XAU per INR, invert to get INR per ounce.
Caching: This example caches for 60 seconds. Tune based on your subscription’s update frequency and your UI’s responsiveness requirements.
Premiums and fees: Keep local adjustments transparent; store both base and adjusted prices so users understand markups.

Historical Kerala Pricing: Valuations, P&L, and Charting

To build Kerala 24k charts or run backtesting, you’ll need historical rates. Metals-API provides historical snapshots and time series data. Once obtained, apply the same INR-per-gram conversion and any Kerala-specific adjustments.

Historical (Single Date) Snapshot

{
"success": true,
"timestamp": 1789432608,
"base": "USD",
"date": "2026-09-15",
"rates": {
"XAU": 0.000485,
"XAG": 0.03825,
"XPT": 0.000915,
"XPD": 0.000748
},
"unit": "per troy ounce"
}

Use this to value inventory at a specific day’s close, audit quotes, or calculate P&L on a single date. If you need INR, either request base=INR (plan-permitting) or run a conversion step.

Time Series (Multi-Day) Backfill

{
"success": true,
"timeseries": true,
"start_date": "2026-09-09",
"end_date": "2026-09-16",
"base": "USD",
"rates": {
"2026-09-09": {
"XAU": 0.000485,
"XAG": 0.03825,
"XPT": 0.000915
},
"2026-09-11": {
"XAU": 0.000483,
"XAG": 0.0382,
"XPT": 0.000913
},
"2026-09-16": {
"XAU": 0.000482,
"XAG": 0.03815,
"XPT": 0.000912
}
},
"unit": "per troy ounce"
}

Recommendations for charting Kerala 24k from this:

Normalize: Convert each XAU daily value to INR/gram using the same formula for consistency across dates.
Weekends/holidays: Expect no changes or repeated values where markets are effectively closed. Smooth or annotate your chart accordingly.
Caching and storage: Persist daily values to your data warehouse for reliable analytics and rapid chart rendering.

Day-to-Day Kerala Movement: Fluctuation for Alerts and Summaries

Fluctuation data captures day-over-day changes without you having to compute deltas manually. It’s ideal for alerting retail teams, traders, or end-users about Kerala 24k price swings.

{
"success": true,
"fluctuation": true,
"start_date": "2026-09-09",
"end_date": "2026-09-16",
"base": "USD",
"rates": {
"XAU": {
"start_rate": 0.000485,
"end_rate": 0.000482,
"change": -3.0e-6,
"change_pct": -0.62
},
"XAG": {
"start_rate": 0.03825,
"end_rate": 0.03815,
"change": -0.0001,
"change_pct": -0.26
},
"XPT": {
"start_rate": 0.000915,
"end_rate": 0.000912,
"change": -3.0e-6,
"change_pct": -0.33
}
},
"unit": "per troy ounce"
}

How to apply for Kerala pricing:

Use the XAU start_rate and end_rate to compute INR/gram deltas. If your base is USD, convert both endpoints to INR/gram before computing changes.
Power user alerts: Trigger push/email messages for thresholds (e.g., more than ±1% daily move).

Precision Quoting: Use Bid/Ask and OHLC for Execution-Aware Workflows

Kerala retail flows can benefit from bid/ask data to shape competitive buy/sell quotes. OHLC supports charting and technical signals uptake.

Bid/Ask (Tighter Buy/Sell Quotes)

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": {
"bid": 0.000481,
"ask": 0.000483,
"spread": 2.0e-6
},
"XAG": {
"bid": 0.0381,
"ask": 0.0382,
"spread": 0.0001
},
"XPT": {
"bid": 0.000911,
"ask": 0.000913,
"spread": 2.0e-6
}
},
"unit": "per troy ounce"
}

Operational tips:

Separate buy vs sell: Compute INR/gram from bid for buy-back quotes and from ask for retail sells, so your spread captures execution cost and risk.
Risk settings: Widen spreads during high volatility windows. Persist timestamp to audit any final quotes.

OHLC (Open/High/Low/Close) for Daily Charting

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": {
"open": 0.000485,
"high": 0.000487,
"low": 0.000481,
"close": 0.000482
},
"XAG": {
"open": 0.03825,
"high": 0.0383,
"low": 0.0381,
"close": 0.03815
},
"XPT": {
"open": 0.000915,
"high": 0.000918,
"low": 0.00091,
"close": 0.000912
}
},
"unit": "per troy ounce"
}

Implementation considerations:

Daily candles: Convert each of open, high, low, close to INR/gram for a clean Kerala chart.
Feature engineering: Use OHLC to compute volatility, ATR, or Bollinger-derived signals that support pricing decisions or inventory hedging.

Converting Between USD, XAU, and INR

The convert endpoint allows straightforward conversions between metals and currencies. Use it to translate order totals or to normalize quotes in your backend.

{
"success": true,
"query": {
"from": "USD",
"to": "XAU",
"amount": 1000
},
"info": {
"timestamp": 1789519008,
"rate": 0.000482
},
"result": 0.482,
"unit": "troy ounces"
}

Kerala flow examples:

Cart checkout: Convert INR to XAU weight or vice versa for a bullion shop’s transparent invoice.
Hedging interface: Convert cash exposures into gold ounces to size futures or OTC hedges.
Reporting: Aggregate positions in a base currency, even when transactions are in grams and INR.

Using the Carat Feature for Purity-Specific Displays

For 24k, XAU already aligns with pure gold. If you need to present 22k or 18k Kerala prices side-by-side, the carat endpoint can help, or you can apply a proportional purity factor (e.g., 22k ≈ 91.67% of 24k content) to the INR/gram base you derived.

Notes:

When using carat-based data, ensure you confirm the interpretation of purity against your retail standard and BIS hallmarking norms.
Always display units and purity next to any price to avoid ambiguity.

Symbols, Units, and Conventions Reference

Item	Meaning	Kerala Use
XAU	Gold per troy ounce	Base for 24k pricing
INR	Indian Rupee	Local Kerala quoting currency
Troy Ounce	31.1034768 grams	Convert to INR/gram for retail
Bid/Ask	Two-sided market	Buy-back vs. retail price
OHLC	Daily candle metrics	Charting and analytics

Review the full symbol set at the Metals-API Supported Symbols page.

Timestamps, Timezones, and Market Hours

Timestamps: Metals-API timestamps are UNIX epoch seconds. Store as UTC; convert to IST in the UI if targeting Kerala users.
Weekend behavior: Don’t assume frequent updates on weekends/holidays. Lock your Saturday/Sunday quotes if liquidity is thin.
Intraday plans: If you subscribe to more frequent updates, align your cache TTL and UI refresh accordingly.

Error Handling and Data Quality Controls

Implement durable error handling and validation to maintain trust with Kerala customers:

Check success flag: Abort workflows if success=false and log details.
Validate rate presence: Ensure rates.XAU is defined for target dates and endpoints.
Fallback logic: If the latest endpoint fails, try using the most recent cached value and annotate the UI as “delayed.”
Outlier detection: Compare current INR/gram to a rolling median to avoid propagating spikes or stale ticks.

Caching, Quotas, and Performance

Server-side caching: Use a shared in-memory cache (e.g., Redis) with TTL tuned to your plan’s update frequency to minimize API calls.
Edge caching: CDN cache for static JSON snapshots (e.g., end-of-day OHLC) to accelerate charts.
Batching: If you need multiple metals, request them in one call using the symbols parameter to reduce round trips.
Backoff strategy: Respect error responses, implement exponential backoff, and retry sparingly to avoid cascading failures.

Security and Key Management

API keys: Treat your access_key as a secret. Do not hard-code in public clients; proxy calls through your backend when possible.
Transport security: Always use HTTPS.
Access controls: In your backend, rate-limit by user or app to shield your quota. Log access for auditability.
Data integrity: Verify response schema and types before using values in pricing logic.

Kerala Market Adjustments: Practical Considerations

Making charges: Add per-gram or percentage premiums after computing INR/gram base from XAU.
GST and local taxes: Apply tax logic last; display a breakdown line in receipts for transparency.
Retail vs wholesale: Use ask for retail pricing and bid for buy-back flows. Show live spread to help customers understand differences.

Operational Playbook: Daily Routines

Morning open: Warm up caches with latest XAU in INR, per-gram conversion precomputed, and updated spreads.
Intraday refresh: Update every N minutes based on plan; debounce UI updates to avoid display flicker.
Close-of-day: Snapshot OHLC, compute daily fluctuation summary, and archive time-series.
Alerts: Send automated alerts for thresholds (e.g., ±1% daily move) to ops and retail staff.

Example: Building a Kerala 24k Ticker Card

Data elements to include:

Kerala 24k INR/gram (adjusted and base values)
Timestamp (IST human-readable)
Daily change (absolute and % from previous close)
Buy (bid-based) and Sell (ask-based) per gram quotes

Data flow:

Fetch latest XAU with base=INR (or USD then convert).
Compute INR/gram.
Fetch bid/ask for XAU; compute INR/gram buy/sell quotes.
Compute change vs previous day’s close (from OHLC or time-series).

End-to-End JSON Examples To Integrate Today

Latest Rates: Base USD, Multiple Metals

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": 0.000482,
"XAG": 0.03815,
"XPT": 0.000912,
"XPD": 0.000744,
"XCU": 0.294118,
"XAL": 0.434783,
"XNI": 0.142857,
"XZN": 0.344828
},
"unit": "per troy ounce"
}

Historical Snapshot: Prior Day Close

{
"success": true,
"timestamp": 1789432608,
"base": "USD",
"date": "2026-09-15",
"rates": {
"XAU": 0.000485,
"XAG": 0.03825,
"XPT": 0.000915,
"XPD": 0.000748
},
"unit": "per troy ounce"
}

Time-Series: One Week Backfill

{
"success": true,
"timeseries": true,
"start_date": "2026-09-09",
"end_date": "2026-09-16",
"base": "USD",
"rates": {
"2026-09-09": {
"XAU": 0.000485,
"XAG": 0.03825,
"XPT": 0.000915
},
"2026-09-11": {
"XAU": 0.000483,
"XAG": 0.0382,
"XPT": 0.000913
},
"2026-09-16": {
"XAU": 0.000482,
"XAG": 0.03815,
"XPT": 0.000912
}
},
"unit": "per troy ounce"
}

Fluctuation: Day-over-Day Change

{
"success": true,
"fluctuation": true,
"start_date": "2026-09-09",
"end_date": "2026-09-16",
"base": "USD",
"rates": {
"XAU": {
"start_rate": 0.000485,
"end_rate": 0.000482,
"change": -3.0e-6,
"change_pct": -0.62
},
"XAG": {
"start_rate": 0.03825,
"end_rate": 0.03815,
"change": -0.0001,
"change_pct": -0.26
},
"XPT": {
"start_rate": 0.000915,
"end_rate": 0.000912,
"change": -3.0e-6,
"change_pct": -0.33
}
},
"unit": "per troy ounce"
}

OHLC: Daily Candle

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": {
"open": 0.000485,
"high": 0.000487,
"low": 0.000481,
"close": 0.000482
},
"XAG": {
"open": 0.03825,
"high": 0.0383,
"low": 0.0381,
"close": 0.03815
},
"XPT": {
"open": 0.000915,
"high": 0.000918,
"low": 0.00091,
"close": 0.000912
}
},
"unit": "per troy ounce"
}

Bid/Ask: Two-Sided Market

{
"success": true,
"timestamp": 1789519008,
"base": "USD",
"date": "2026-09-16",
"rates": {
"XAU": {
"bid": 0.000481,
"ask": 0.000483,
"spread": 2.0e-6
},
"XAG": {
"bid": 0.0381,
"ask": 0.0382,
"spread": 0.0001
},
"XPT": {
"bid": 0.000911,
"ask": 0.000913,
"spread": 2.0e-6
}
},
"unit": "per troy ounce"
}

Convert: USD to XAU

{
"success": true,
"query": {
"from": "USD",
"to": "XAU",
"amount": 1000
},
"info": {
"timestamp": 1789519008,
"rate": 0.000482
},
"result": 0.482,
"unit": "troy ounces"
}

Real-World Scenarios and Best Practices

Scenario 1: Retail Website for Kerala 24k

Data: Latest XAU base=INR, Bid/Ask, OHLC close for “yesterday.”
Display: INR/gram 24k with “As of [IST time],” daily change vs yesterday close, buy/sell toggle showing spread-derived quotes.
Performance: Cache latest for 30–60s, daily OHLC for the day. Batch symbol requests where possible.

Scenario 2: ERP Stock Valuation

Data: Historical or OHLC close for the valuation date.
Process: Convert to INR/gram, apply purity mapping for non-24k SKUs, and store valuations in ledger.
Compliance: Log timestamps and source for audit.

Scenario 3: Trading and Hedging Desk

Data: Intraday-enabled plans for lower latency, Bid/Ask for spreads, Fluctuation to track daily P&L dynamics.
Workflow: Use convert to translate order sizes between INR and ounces for hedges.
Controls: Implement alerting and circuit breakers on extreme moves.

Data Validation, Sanitization, and Monitoring

Schema validation: Enforce JSON schema for all responses. Treat missing fields as hard failures.
Type checks: Convert numbers, guard against NaN/Infinity before arithmetic.
Monitoring: Track update latency (now - timestamp), response time, error rates, and cache hit ratios.
Traceability: Persist raw payloads and computed INR/gram for forensics and customer support.

Handling Market Closures and Special Events

Static weekends: Pre-announce in UI that weekend updates are limited; show last updated time prominently.
High-volatility events: Temporarily widen spreads or pause auto-refresh if upstream markets are unstable.
Maintenance windows: Implement banner notifications if your app is using cached or delayed data.

Scaling Your Pricing Platform

Horizontal scaling: Stateless services for fetch/transform; use managed cache and message queues.
Data lake: Store daily OHLC and historical series for analytics and ML without repeatedly hitting the API.
Sharding by region: If you price for multiple Indian states, keep shared gold core while varying tax and fee rules per region.

Innovation in Gold Price Discovery and Digital Transformation

Kerala’s gold ecosystem can benefit from a modern data stack:

Dynamic pricing: Use Metals-API data to drive in-store display boards and online stores with synchronized updates.
Analytics: Compute customer-facing signals—daily change, 7-day trend, volatility—and embed insights into the product experience.
Digital asset solutions: Back tokenized gold SKUs with auditable XAU-linked rates, converting to INR/gram for compliance and customer clarity.
Technology integration: Stream data into fintech tools, wealth apps, and jewelry ERPs for unified operations.

Practical Links and Resources

Product overview and signup: Metals-API Website — get your free API key to start building.
Parameter and endpoint reference: Metals-API Documentation
Symbols catalog: Metals-API Supported Symbols
Background on troy ounces: LBMA Good Delivery and measurement guidance
India market context: BIS Hallmarking resources

Conclusion: Build a Reliable Kerala 24k Pipeline with Metals-API

To assemble Kerala Gold 24k (KERA-24k) pricing across markets, combine the XAU reference with INR conversion and, when needed, carat-based purity logic and local adjustments. Metals-API provides the real-time and historical backbone—Latest for live ticks, Bid/Ask for executable spreads, OHLC for charting, Time Series and Historical for backfill, Fluctuation for alerts, and Convert for cross-unit totals. Implement robust units handling (troy ounce to grams), timestamps in UTC/IST, caching tuned to your plan, and clear error handling to keep your quotes stable and trustworthy. Get started now at the Metals-API Website, read through the Metals-API Documentation, and ship your Kerala 24k pricing experience with confidence.

FAQ

Is there a dedicated “KERA-24k” symbol in Metals-API?

No. Use XAU as the gold reference, set INR as the base where supported, convert to INR/gram, and apply any Kerala-specific adjustments within your application logic.

What unit are metals quoted in?

Per troy ounce. Convert to grams using 1 troy ounce = 31.1034768 grams for retail display.

How do I compute a per-gram Kerala price?

Derive INR per ounce from XAU and base=INR (or by converting USD to INR), then divide by 31.1034768. Add making charges, taxes, and margins as per your business rules.

How can I show buy and sell prices?

Use bid for buy-back quotes and ask for retail sell quotes. Convert each side independently to INR/gram.

How do I handle weekends and holidays?

Expect fewer or no updates; use last known price and clearly display the timestamp and “as of” labeling. Avoid misleading “live” tags during closures.

Where can I find a list of supported symbols and params?

Visit the Metals-API Supported Symbols and the Metals-API Documentation for parameter details.

Can I backfill price history for analytics?

Yes. Use Historical for snapshots and Time Series for ranges. Store results and convert to INR/gram for consistent charting.

How do I get started?

Sign up for your API key at the Metals-API Website, explore the docs, and integrate the Latest, Bid/Ask, OHLC, Time Series, and Convert features into your Kerala 24k workflow.

Ready to use Metals-API?

Try it now!