Get Accurate Pakistan Gold 22k (XAUPAK22) Prices in Multiple Currencies with this API

Building a pricing workflow for Pakistan Gold 22k that updates in real time and shows values in multiple currencies is a classic integration challenge for trading tools, jewelry e-commerce, and ERP systems. With Metals-API, you can compute accurate 22 karat gold valuations from the benchmark Gold (XAU) price and stream them into dashboards, catalogs, and risk models. This guide shows how to source the base XAU price, calculate 22k (91.67% purity) in PKR and other currencies, handle intraday and historical views, and operationalize the pipeline end to end — including data units, timestamps, carat handling, caching, and market-closure edge cases. You’ll also see how to expand beyond spot to OHLC, Bid/Ask, fluctuation, and time series, plus practical considerations for fintech-grade reliability. If you’re here for the short version: you’re not looking for a bespoke symbol like “XAUPAK22”; instead, you’ll derive 22k (Pakistan standard) from XAU and combine it with your target fiat currencies.

Why “Pakistan Gold 22k” is a derived price — and why that’s good for accuracy

There isn’t a single canonical symbol like XAUPAK22 that exists on global feeds. Instead, the market convention is to price pure gold (XAU, 24 karat) in a reference base currency, and then compute 22k (which is 22/24 purity, or 0.9167) and local-currency equivalents. That separation keeps your model auditable and flexible. Metals-API delivers:

Real-time and historical Gold (XAU) rates with consistent units (per troy ounce) and timestamps.
Currency conversion rates alongside metals prices so you can show PKR, USD, AED, SAR, GBP, EUR, and more.
Specialized endpoints for OHLC, bid/ask, time series, and fluctuations for richer analytics and UX.

You’ll combine XAU with karat percentage and then apply currency conversion to display 22k per troy ounce, per tola, per gram, or per item. This approach is reproducible across Pakistan’s market context and any other regional standard. You can start in minutes — get a free API key from the Metals-API Website and review the reference on the Metals-API Documentation.

Core workflow: from XAU to Pakistan Gold 22k in multiple currencies

Here is the standard pipeline most teams adopt:

Fetch base Gold (XAU) spot data using Latest Rates, OHLC, Intraday, or Bid/Ask depending on your UX.
Convert 24k (XAU) to 22k by applying the purity factor 22 / 24 = 0.9167.
Convert 22k price into your target currencies (PKR primary; optionally USD, AED, SAR, EUR, GBP, JPY, etc.).
Normalize units (troy ounce, gram, tola) and display consistently in your interface.
Store historical snapshots for charts and P&L (via Historical Rates or Time-Series).
Add analytics like day-over-day Fluctuation or OHLC candlesticks to enrich decision-making.

Key tip: Do not hard-code conversions or purity math into templates — keep it in one service layer so you can change the business logic universally (e.g., add making charges, VAT/GST, or jeweler margin) without refactoring every frontend or report.

Understanding XAU data and units (troy ounces, grams, tolas)

Metals-API returns metal rates in units “per troy ounce,” a standard in bullion markets. Many retail contexts in Pakistan reference grams or tolas (11.664 grams). To avoid confusion:

1 troy ounce = 31.1034768 grams
1 tola (Pakistan jewelry context) ≈ 11.664 grams

After you fetch XAU per troy ounce, compute your downstream units by deterministic multiplication or division. If your UI shows per gram 22k PKR, be explicit in labels and documentation, and keep that logic identical across tools so traders and product managers get the same number everywhere.

Where to find symbols and plan your integrations

Before building, confirm symbols and metals coverage on the Metals-API Supported Symbols page. You’ll use XAU for gold. For currency coverage and implementation details (including request parameters), use the authoritative Metals-API Documentation. If you’re integrating across departments (trading, e-commerce, and ERP), plan a single internal standard for symbols, base currency, and unit display to avoid data fragmentation.

Anchoring the 22k Pakistan price to XAU: practical calculation

Conceptually:

XAU per USD (as returned by Latest Rates) tells you how many ounces of gold you get per 1 USD.
USD per ounce is 1 / (XAU per USD).
22k per ounce in USD = (USD per ounce at 24k) × 0.9167.
Convert to PKR (or other currencies) using currency rates.

This separation lets you produce a robust “Pakistan 22k” view while retaining transparency to the underlying XAU benchmark. Your pricing audit trail stays clean: XAU source, timestamp, rates, conversion, and karat math are all inspectable.

Fetching live XAU rates for 22k Pakistan price streams

For real-time UIs and automated workflows, the Latest Rates endpoint provides current XAU pricing. Frequency depends on your plan tier. Below is an example of a Latest response payload you’ll parse to obtain XAU:

Latest Rates example (XAU, XAG, XPT etc.)

{
"success": true,
"timestamp": 1789520203,
"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"
}

Fields you’ll use:

success: Boolean for request status.
timestamp: Unix epoch (seconds). Use this for caching and charting; be mindful of timezone in your app display.
base: The reference currency for the rates (USD by default).
date: ISO-8601 date associated with the snapshot.
rates.XAU: Gold per USD per troy ounce.
unit: Explicitly “per troy ounce.”

Common pattern to compute USD per ounce:

usd_per_ounce_24k = 1 / rates.XAU
usd_per_ounce_22k = usd_per_ounce_24k × (22 / 24) = usd_per_ounce_24k × 0.9167

To show PKR or other currencies, combine the above with your currency conversion step (discussed below). If you cache or snapshot this response, store the entire JSON with a hash of your business logic version; this is critical for forensic reconciliation.

Complete curl to retrieve current rates

Replace YOUR_API_KEY with your key from the Metals-API Website.

curl -s "https://metals-api.com/api/latest?access_key=YOUR_API_KEY"

Tip: Integrate exponential backoff and graceful degradation if your UI relies on real-time updates. Also, apply a short TTL cache (e.g., 30–60 seconds depending on plan granularity) to amortize load across users while staying within freshness SLAs.

Converting to 22k and multiple currencies programmatically

The Convert endpoint is designed to transform amounts between currencies and metals. Below is a canonical Convert response example. While this sample demonstrates a USD to XAU conversion, the same principle applies when building multi-currency 22k outputs after calculating your USD per ounce baseline.

Convert example (USD → XAU)

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

Fields to note:

query: Echoes your conversion intent (from, to, amount).
info.timestamp: The rate timestamp used for conversion; align this with your XAU feed to ensure consistency across chained computations.
info.rate: The rate applied for conversion.
result: The converted amount (e.g., ounces from dollars).
unit: For metals, operations are in troy ounces.

Practical tip: When building multi-currency 22k displays (PKR, AED, SAR, etc.), standardize your pipeline to:

Get spot XAU.
Derive 24k USD per ounce, then 22k USD per ounce.
Convert USD → target fiat using consistent timestamps.

Keep timestamps aligned to avoid basis mismatches between metal and FX components. Where possible, derive all currencies from a single composite snapshot to maintain internal consistency.

JavaScript example: deriving 22k prices and converting units

The following snippet illustrates how to take a Latest Rates response, compute 22k pricing per ounce, per gram, and per tola, and then prepare for currency conversion. Use your own conversion step for PKR and other fiats based on your application’s design.

// Assume you fetched the Latest Rates JSON above as `latest`
const latest = {
success: true,
timestamp: 1789520203,
base: "USD",
date: "2026-09-16",
rates: { XAU: 0.000482 },
unit: "per troy ounce"
};

// Constants
const TROY_OUNCE_TO_GRAM = 31.1034768;
const TOLA_TO_GRAM = 11.664;
const KARAT_22_FACTOR = 22 / 24; // 0.916666...

// Compute 24k and 22k in USD per troy ounce
const xauPerUsd = latest.rates.XAU; // ounces per 1 USD
const usdPerOunce24k = 1 / xauPerUsd; // USD per ounce (24k)
const usdPerOunce22k = usdPerOunce24k * KARAT_22_FACTOR;

// Convert to per gram and per tola (USD)
const usdPerGram22k = usdPerOunce22k / TROY_OUNCE_TO_GRAM;
const usdPerTola22k = usdPerGram22k * TOLA_TO_GRAM;

// Next step: convert USD → PKR (or AED, SAR, etc.) using your currency rates
// Example placeholder function:
// const pkrPerUsd = ... // fetch from Metals-API currency rates
// const pkrPerOunce22k = usdPerOunce22k * pkrPerUsd;
// const pkrPerGram22k = usdPerGram22k * pkrPerUsd;
// const pkrPerTola22k = usdPerTola22k * pkrPerUsd;

console.log({
date: latest.date,
usdPerOunce22k,
usdPerGram22k,
usdPerTola22k,
unitBase: "USD",
metalUnit: "troy ounce",
purity: "22k"
});

Operational note: expose the purity factor in configuration so you can support 21k, 18k, or custom assays if you price recycled scrap or specific retail SKUs.

Historical context for Pakistan 22k pricing: backfill, charts, and analytics

To backfill historical charts (e.g., a 1-year PKR 22k per tola chart), use Historical Rates and Time-Series. You’ll compute 22k values on top of the historical XAU snapshots. This gives you consistency with your real-time logic and avoids mixing third-party formulas.

Historical Rates example (single day)

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

Use cases:

Backfill daily close values of 22k per gram and per tola for Pakistan store pricing histories.
Compute historical implied spreads or volatility measures for risk dashboards.
Recreate P&L for hedged/unhedged positions in manufacturing or jewelry inventory.

Time-Series example (date range)

{
"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"
}

Implementation guidance:

Map over daily XAU values, compute 24k → 22k, then convert to PKR with that day’s FX rate for consistency.
Use day-level caches to accelerate multi-tenant chart loads.
If you display weekend points, note that metals markets may be closed; decide whether to interpolate, forward-fill, or omit dates to maintain visual clarity.

Adding trading context: OHLC bars and intraday microstructure

If you present candlestick charts or intraday analytics, the OHLC and Intraday features add depth to your Pakistan 22k view. You’ll apply the same 24k → 22k computation to the open, high, low, and close values and then convert to PKR or other currencies for display.

OHLC example

{
"success": true,
"timestamp": 1789520203,
"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"
}

Common usage:

Compute 22k OHLC by applying the 0.9167 factor to each component (after converting to USD/ounce if needed).
Emit consistent timestamps and timezones in your UI (UTC recommended) with a clear legend.
If you allow users to switch between ounce, gram, and tola in the chart, apply the unit conversions uniformly to all OHLC values.

Intraday granularity helps execution algos and dealer quotes. Use it to refine alerts (e.g., if 22k PKR per tola breaches a threshold intraday). Check the Metals-API Documentation for your plan’s intraday capabilities.

Bid/Ask spreads for retail and B2B quoting

Market makers and jewelers often reference bid/ask spreads when quoting customers or when revaluing inventory. Metals-API provides Bid/Ask for relevant symbols so you can build robust price stacks.

Bid/Ask example

{
"success": true,
"timestamp": 1789520203,
"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"
}

Best practices:

Pick a side for inventory valuation (bid or mid) and document it. Many use mid for P&L and ask for buy-side customer quotes.
For Pakistan 22k storefronts, display the 22k ask for consumers and optionally annotate the basis to maintain transparency.
Feed the bid/ask into your hedging logic to avoid underestimating transaction costs.

Measuring change: Fluctuation for Pakistan 22k moves and alerts

Day-over-day change is a simple but powerful signal for merchandising decisions, risk thresholds, and user alerts. Metals-API has a Fluctuation feature that gives start/end rates and absolute/percentage changes over a period.

Fluctuation example

{
"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"
}

Turn this into 22k PKR movement by applying the same purity and currency conversions at start and end. Then produce change and change_pct on the final values your users see. This aligns the reported movement with what buyers and managers care about: “How did 22k per tola in PKR change this week?”

Detecting extremes for quality checks and anomalies

The Lowest/Highest Price feature helps validate feeds and identify anomalies. After you calculate 22k prices from baseline XAU, you can test whether today’s 22k per gram in PKR falls outside a trailing band. If yes, you can trigger manual verification steps or adjust quote aggressiveness. Pair this with OHLC and Fluctuation to triangulate outliers.

Gold carats by endpoint: how to model 22k programmatically

Metals-API includes a Carat feature to retrieve gold rates by carat. This is ideal when your business logic revolves around retail karat systems. For Pakistan 22k, you can standardize on the 22/24 purity and ensure all charts, widgets, and pricing services reference the same factor. When building your architecture:

Centralize purity factors in a single constants service (e.g., 24k = 1.0, 22k = 0.9167, 21k = 0.875, 18k = 0.75).
Keep audit logs for any purity factor changes to ensure compliance and customer trust.
In multi-country rollouts, parameterize the karat factor so localized products don’t diverge from global standards.

For detailed usage patterns and integration specifics, consult the Metals-API Documentation. Validate assumptions against your internal QA dataset before going live.

Architecting the “Pakistan 22k in multiple currencies” service

A typical high-reliability architecture includes:

Ingestion layer: Scheduled pull of Latest, Intraday, Bid/Ask, or OHLC depending on requirements.
Normalization: Convert XAU per USD to USD per ounce, then apply 22k purity factor.
FX layer: Attach synchronized fiat conversions for PKR and secondary currencies.
Unit transforms: Derive per gram and per tola alongside per ounce.
Caching: Use multi-tier caches (memory + Redis) with TTLs tailored to update frequency.
Persistence: Store raw responses and computed snapshots (plus signatures/hashes for auditing).
API surface: Expose a clean internal endpoint for frontend/apps (e.g., GET /gold/pakistan/22k?unit=tola&currency=PKR).
Monitoring: Alert on missing fields, extreme spreads, stale timestamps, and divergence from expected ranges.
Resilience: Implement fallback logic and graceful degradation modes (e.g., last good value with “stale” tag in UI).

Weekend and market-closure handling

Metals markets observe closures. Decide up front:

Do you forward-fill the last close for Saturday/Sunday dashboards?
Should intraday widgets pause with a “market closed” banner?
How do you label stale values in PKR 22k to protect operational decisions?

Be explicit in the UI and in your API responses. Include the upstream timestamp from Metals-API responses to ensure every downstream user understands data freshness.

Caching and performance: how to save requests and accelerate UX

Performance strategies that work well in production:

Short TTL for real-time endpoints; longer TTL for historical/time-series.
Consolidate multi-currency requests into a single backend call and fan-out internally.
Persist hourly snapshots for “time travel” debugging across services.
Use ETag-style hashing on normalized payloads to skip redundant recomputations.
Defer unit conversions to the edge if your CDN or edge workers can safely host deterministic math.

Security and keys

Treat your Metals-API access key as a secret. Best practices:

Store keys in a secure vault (e.g., managed KMS, Vault) and inject at runtime.
Never embed keys in mobile/web clients; route calls through your backend.
Rate-limit and log all egress from your integration layer to detect anomalies.
Rotate keys periodically and on personnel changes.

Error handling and resilience

Build robust clients that expect occasional network or upstream errors:

Check success flags and status codes; on failure, log details (without exposing secrets) and retry with backoff.
Validate that required fields (e.g., rates.XAU) exist before computing 22k.
Fallback to the last known good snapshot with a visible “stale” indicator if necessary.
Alert when deltas exceed sane thresholds (e.g., price jumps beyond historical vol bands) to catch data anomalies early.

Data validation and sanitization

Before persisting or displaying:

Confirm numeric types and ranges for rates, timestamps, and computed values.
Ensure unit labels match the math applied (ounce/gram/tola).
Normalize date formats (ISO-8601) and timezones (UTC) across your system.
Hash each normalized record to detect phantom changes in caches or storage.

End-to-end example: build a PKR 22k price card with day-over-day change

Fetch Latest for XAU.
Compute USD per ounce 24k and then 22k.
Apply USD→PKR conversion (from your synchronized currency rates snapshot).
Compute per gram and per tola from per ounce.
Fetch Fluctuation or two Historical snapshots for previous day, compute 22k in PKR for that day.
Compute change and percentage; present as green/red delta next to today’s 22k PKR per tola.

Ensure all components share the same effective timestamp set so movements reflect genuine market dynamics, not asynchronous data pulls.

Putting it all together: a complete operational checklist

Acquire and securely store your API key from the Metals-API Website.
Confirm symbols and required endpoints via the Metals-API Supported Symbols and Metals-API Documentation.
Implement Latest, Historical, Time-Series, OHLC, Bid/Ask, and Fluctuation as needed for your UX.
Centralize purity (22k) and unit conversions (ounce/gram/tola) in a single shared module.
Design a synchronized snapshot strategy to keep metals and FX aligned in time.
Add caching layers and backoff retries to control costs and increase reliability.
Instrument alerts for stale data, extreme spreads, and anomalous movements.
Document every step so pricing, trading, and finance teams share a consistent mental model.

Additional resources

Quick reference: endpoint behaviors and implementation notes

Latest: Real-time spot snapshot. Use for current 22k quotes. Cache tightly and align timestamps.
Historical: Single date. Use for previous close and P&L checkpoints.
Time-Series: Range of daily snapshots. Use for backfills and charts.
Fluctuation: Start/end change. Use for deltas and alerting.
OHLC: Candlestick components. Use for technical analysis and detailed charting.
Bid/Ask: Market microstructure. Use for quoting and transaction-cost modeling.
Convert: Flexible conversions. Use for fiat/metal transforms when building multi-currency outputs.
Carat: Streamline karat-based pricing. Centralize purity handling for retail-ready gold SKUs.

Example-driven field explanations you will actually use

Across the API responses shown above, the most operationally critical fields are:

timestamp: Always store and surface it. It underpins caching, reconciliation, and process control.
base: Keep track of the reference currency for correct inversion and conversions.
rates.XAU (or nested OHLC/Bid/Ask objects): Your primary input for deriving 22k values.
unit: Consistently “per troy ounce”; it’s your anchor for unit conversions.
date/start_date/end_date: For labeling chart axes and ensuring period alignment.
change/change_pct (Fluctuation): Build your KPI tiles and thresholds around these.

A note on digital transformation and analytics for gold (XAU)

Gold pricing has moved beyond static tickers. Developers now orchestrate end-to-end data flows that turn raw XAU into product-level signals: dynamic price tags for jewelry sites, ERP revaluations, trade decision support, and CFO dashboards. Metals-API is a backbone for this transformation: standardized JSON, multi-endpoint coverage, and predictable timestamps foster reproducible analytics. Layer in OHLC and Bid/Ask for richer insights, and your Pakistan 22k pipeline becomes not just a display but an operational decision engine — from hedging and procurement to merchandising and customer trust. With the right abstractions, you can extend the same stack to silver, platinum, and industrial metals that matter in electronics and manufacturing.

Troubleshooting common pitfalls

Wrong units in UI: Double-check ounce/gram/tola math. Add unit tests for each conversion branch.
Inconsistent currency rates: Ensure FX and metals snapshots share timestamps to avoid phantom moves.
Weekend “flatline”: Mark market closures and use forward-fill visibly; document behavior in tooltips.
Surprise spikes: Cross-check Bid/Ask and OHLC; apply outlier guards and manual review triggers.
Stale cache: Monitor TTLs against plan update frequency; alert when timestamp lags beyond tolerance.
Key leakage: Never expose keys in client apps; proxy through your secured backend only.

Conclusion

Delivering accurate Pakistan Gold 22k prices across multiple currencies starts with a clean, auditable foundation: XAU spot data, a clear purity factor, synchronized fiat conversions, and disciplined unit handling. Metals-API gives you the endpoints you need — Latest for real-time, Historical and Time-Series for backfills, Fluctuation for movement analytics, OHLC and Bid/Ask for trading context, and Carat support for retail-ready outputs. Wrap these with caching, validation, and clear UX signals, and you’ll have a resilient pricing service that scales from a single storefront widget to enterprise-grade ERP and trading use cases. Get started now with your free key at the Metals-API Website and dig into endpoint specifics in the Metals-API Documentation.

FAQ

Is there a single symbol like XAUPAK22 I can query?

Market convention is to price pure gold (XAU, 24k) and then derive karat values (e.g., 22k) via purity factors, finally converting to local currencies like PKR. That approach is transparent and auditable. Use XAU data and compute 22k (22/24) within your service.

How do I convert from ounce to gram or tola?

Use fixed constants: 1 troy ounce = 31.1034768 grams; 1 tola ≈ 11.664 grams. Apply conversions consistently after computing the 22k price per ounce.

Which endpoint is best for a live storefront price?

Use Latest for the headline number, optionally Bid/Ask if you want to reflect spread. Add Fluctuation for daily change badges. Cache responses to meet performance and cost goals.

What about historical charts for Pakistan 22k in PKR?

Pull Historical or Time-Series XAU snapshots, compute 22k and then convert to PKR with synchronized FX rates for each day. This ensures charts match your live pricing logic.

How do I alert on big moves in 22k PKR?

Use Fluctuation or compare consecutive snapshots. Derive 22k for both points and compute change/change_pct on the PKR-translated values. Add thresholds to trigger notifications.

How do I handle market closures and weekends?

Decide whether to forward-fill the last close and clearly label data as stale. Avoid misleading intraday visuals when markets are closed.

Can I use Metals-API for other metals and currencies?

Yes. The same architecture extends to silver (XAG), platinum (XPT), palladium (XPD), and base metals. Currency coverage is broad; see the supported symbols list.

Where can I find all parameters and limits?

Consult the official documentation for request parameters, examples, and plan capabilities. Secure a free API key at the Metals-API site and start testing immediately.

Ready to use Metals-API?

Try it now!