Home
Blog
Get Palladium Ask (XPD-ASK) prices in various currencies using this API

Get Palladium Ask (XPD-ASK) prices in various currencies using this API

Get Palladium Ask (XPD-ASK) prices in various currencies using this API

If you quote or hedge Palladium in multiple currencies, you need reliable XPD Ask prices you can plug into pricing, risk, and supply chain systems without gaps. This guide shows exactly how to retrieve Palladium Ask (XPD-ASK) quotes in USD, EUR, JPY, GBP and beyond using the Metals-API, and how to integrate that data into order execution, catalog pricing, analytics dashboards, and ERP workflows. We’ll cover live bid/ask retrieval, historical backfills, intraday refresh, OHLC, time series analytics, fluctuation analysis, and precise unit conversions, plus caching, error handling, and weekend behavior—so your developers can build resilient, production-ready integrations fast.

Why real-time Palladium Ask prices power modern automotive and manufacturing stacks

Palladium (symbol XPD) sits at the center of catalytic converter innovation, emissions abatement, and increasingly intelligent manufacturing lines. As automotive technology moves to smarter powertrains and tighter environmental standards, enterprises must monitor Palladium in real time to:

  • Reprice configurable products and catalytic assemblies in ecommerce, CPQ, and dealer portals.
  • Trigger hedging strategies as spreads change intra-day, especially for XPD-ASK in EUR, JPY, and CNY.
  • Backfill charts, dashboards, and VaR models for procurement, treasury, and trading desks.
  • Automate supply chain actions in ERPs (SAP, Oracle, Microsoft Dynamics) when Palladium crosses budget bands.
  • Feed data science models forecasting catalyst demand, substitution risk with platinum, or emissions credit impacts.

With Metals-API you can retrieve Palladium Ask quotes consistently, with ISO-like metal symbols and standardized JSON across endpoints, making it trivial to integrate with your existing microservices, event-driven pipelines, or data warehouses. Explore the service and get a free API key at the Metals-API Website and review request/response details in the Metals-API Documentation.

What you’ll build: a multi-currency Palladium Ask workflow

We’ll implement a simple, production-grade pattern:

  1. Pull current XPD Ask in USD via the Bid/Ask feature for a live quote.
  2. Convert to any fiat currency (e.g., EUR) reliably using the Convert feature.
  3. Backfill historical, time series, OHLC, and fluctuation data for analytics and risk.
  4. Implement caching and retries for resiliency and cost efficiency.
  5. Normalize units (troy ounces vs grams) and handle timestamps and weekend behavior explicitly.

All examples use official JSON shapes from Metals-API. Symbols and endpoints are documented here: Metals-API Supported Symbols. For clarity, we’ll focus on XPD (Palladium) and touch on XAU (Gold) as a baseline comparison for certain endpoints and unit notes.

Authentication, base currency, units, and timestamps

  • Authentication: Include your access key via the access_key query parameter. Get one at the Metals-API Website.
  • Base currency: By default, exchange rates are relative to USD. That means the “rate” values are quoted as units of the asset per 1 USD.
  • Units: Metals are quoted per troy ounce, not grams. 1 troy ounce = 31.1034768 grams. The API returns a unit field so you can confirm.
  • Timestamps: All responses include a UNIX-like timestamp and a date string. Treat times as UTC when storing and scheduling refreshes.

Core endpoints you’ll use for Palladium Ask and analytics

Metals-API provides a set of focused endpoints that together cover real-time pricing, historical queries, conversions, OHLC, fluctuation analysis, intraday detail, and more. Below, we’ll integrate the Bid/Ask, Latest, Historical, Time-series, Convert, Fluctuation, OHLC, Lowest/Highest, Intraday, and Supported Symbols features into realistic Palladium workflows. Feature availability and update frequency can vary by subscription; see the Metals-API Documentation for plan-specific details.

Quick reference: common symbols for pricing Palladium Ask across currencies

Symbol Description Typical Use
XPD Palladium Bid/Ask, Latest, Historical, OHLC, Time Series
USD United States Dollar Default base for rates; common settlement currency
EUR Euro European product pricing and hedging
JPY Japanese Yen Automotive supply in Japan
GBP British Pound UK manufacturing and treasury

Step 1: Retrieve live Palladium Ask (XPD-ASK) in USD

The Bid/Ask feature returns current bid, ask, and spread for metals. For Palladium, the ask price represents the current offer—what you’d typically pay to buy Palladium at that moment (subject to your execution venue and logistics). Response values are expressed per troy ounce relative to the base currency (default USD).

Example: Bid/Ask request for Palladium Ask

Request the current XPD bid/ask with USD as base. Replace YOUR_KEY with your access key.

curl -sG "https://metals-api.com/api/bid-ask" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD"

Sample Bid/Ask JSON (structure based on Metals-API)

{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"rates": {
"XPD": {
"bid": 0.000742,
"ask": 0.000746,
"spread": 4.0e-6
}
},
"unit": "per troy ounce"
}

Important fields you’ll use:

  • rates.XPD.ask: The Palladium Ask in units of XPD per 1 USD. To compute USD per ounce, invert the rate: 1 / 0.000746 ≈ USD price per troy ounce. Keep floating-point precision in mind and use decimal libraries where appropriate.
  • unit: Always confirm you’re working per troy ounce when converting to grams or kilograms.
  • timestamp/date: Use for cache keys, reconciliation, and temporal joins in your analytics stack.

Plan for spread-aware logic: For quotes and P&L, store bid, ask, and derived mid = (bid + ask) / 2. Switching to mid for modeling and ask for procurement can reduce confusion and align with your hedging policy.

Step 2: Convert Palladium Ask into another currency (e.g., EUR)

You can convert a USD-based Palladium amount into any target currency with the Convert feature. This is particularly useful when quoting part prices in customer-local currencies or consolidating budgets across subsidiaries.

Example: Convert 10 troy ounces of Palladium to EUR

curl -sG "https://metals-api.com/api/convert" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "from=USD" \
--data-urlencode "to=EUR" \
--data-urlencode "amount=1"

The Convert feature is currency-focused. To convert Palladium exposures, you commonly combine Bid/Ask (to derive a USD value for your ounces) and then convert that USD value to your target currency. Alternatively, if your workflow directly supports metal-to-fiat conversions using the API’s rate semantics, align with the exact documentation for parameterization. A typical pattern:

  1. Obtain XPD Ask rate per 1 USD (from Bid/Ask).
  2. Invert it to compute USD per ounce, then multiply by your ounces.
  3. Convert that USD amount to the target currency using Convert.

Sample Convert JSON

{
"success": true,
"query": {
"from": "USD",
"to": "EUR",
"amount": 1000
},
"info": {
"timestamp": 1789431856,
"rate": 0.9185
},
"result": 918.5,
"unit": "troy ounces"
}

Field usage notes:

  • info.rate: The FX rate used (EUR per 1 USD in this example). Store it to ensure auditability.
  • result: Your converted amount in target currency. When converting values derived from metals, consistently label the step in logs: “XPD to USD” then “USD to EUR”.

Step 3: Build reliable pipelines with Latest, Historical, Time-series

Real-time is only half the equation. For analytics, compliance, and dashboards, you need historical and time-windowed data. Metals-API exposes cohesive JSON across its data features, so your warehousing and BI pipelines remain simple.

Get the latest rates for metals including Palladium

Use Latest for fast refresh of spot-like rates (updated at plan-specific intervals). This endpoint is rate-efficient for general snapshotting and non-spread-aware contexts. For spread-exacting execution logic, prefer Bid/Ask.

curl -sG "https://metals-api.com/api/latest" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD,EUR,JPY,GBP"

Sample Latest JSON (includes XPD)

{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"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"
}

With Latest, you’ll generally:

  • Use rates.XPD to compute indicative values when exact spread is not required.
  • Store timestamp and date for ETL consistency and latency tracking.
  • Treat unit as a schema field in your data models to prevent unit errors in downstream services.

Retrieve a single historical date for audit or backfill

Need to reconstruct end-of-day results or verify an invoice from last quarter? The Historical feature returns per-day data relative to USD by default.

curl -sG "https://metals-api.com/api/2026-09-14" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD"

Sample Historical JSON

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

Practical tip: When backfilling, standardize all dataset timestamps to UTC midnight for the business date. If you blend with intraday sources, maintain a column for “as of” vs “start of day” to avoid duplicate joins.

Pull multi-day windows with Time-series for analytics

For charting and factor models, the Time-series feature returns daily rates between start_date and end_date. This is the simplest way to populate BI dashboards with Palladium history.

curl -sG "https://metals-api.com/api/timeseries" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "start_date=2026-09-08" \
--data-urlencode "end_date=2026-09-15" \
--data-urlencode "symbols=XPD"

Sample Time-series JSON

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

Usage pattern:

  • Loop dates in rates, extract XPD when present. Handle missing days (weekends/holidays) gracefully—don’t assume continuity.
  • Backfill logic: If a date is absent, either carry-forward the most recent business day or leave a null based on your analytics requirements.

Step 4: Quant-oriented analytics with Fluctuation, OHLC, Lowest/Highest

When you move beyond spot reads into alerting, risk analysis, and strategy testing, the Fluctuation, OHLC, and Lowest/Highest features provide compact, targeted payloads that simplify both storage and query logic.

Monitor daily deltas with Fluctuation

Fluctuation summarizes changes between two dates for specified symbols. Use this for threshold-triggered alerts (e.g., “XPD Ask moved more than 1.5% since yesterday”).

curl -sG "https://metals-api.com/api/fluctuation" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "start_date=2026-09-08" \
--data-urlencode "end_date=2026-09-15" \
--data-urlencode "symbols=XPD"

Sample Fluctuation JSON

{
"success": true,
"fluctuation": true,
"start_date": "2026-09-08",
"end_date": "2026-09-15",
"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"
}

For Palladium, you’ll read the same fields under rates.XPD. Use change_pct for normalized comparisons across metals and currencies; it’s robust for watchlists and email/SMS alerts.

Get Open/High/Low/Close with OHLC

OHLC packages intraday dynamics into a compact daily bar. Use this for charting, backtesting signals, or risk summaries.

curl -sG "https://metals-api.com/api/open-high-low-close/2026-09-15" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD"

Sample OHLC JSON

{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"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"
}

For XPD, you’ll read open/high/low/close under rates.XPD. Tip: If you compute returns, clearly label which field you use (close-to-close, open-to-close, etc.). Mixing definitions can invalidate backtests.

Identify intraperiod extremes with Lowest/Highest

The Lowest/Highest feature returns the extreme values for a given date. This is useful for risk band detection and setting dynamic safety stock or pricing buffers.

curl -sG "https://metals-api.com/api/lowest-highest/2026-09-15" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD"

Sample Lowest/Highest JSON

{
"success": true,
"date": "2026-09-15",
"base": "USD",
"rates": {
"XPD": {
"lowest": 0.000738,
"highest": 0.000752
}
},
"unit": "per troy ounce"
}

Use cases: trigger alerts when XPD breaches prior extremes; feed risk dashboards with “distance from low/high” metrics for procurement timing.

Intraday detail and exchange micro-timing

When integrating with smart manufacturing or treasury bots, you may need finer-grained updates during the trading day. The Intraday feature provides data for a single symbol with increased temporal resolution (availability varies by plan).

Query intraday for Palladium

curl -sG "https://metals-api.com/api/intraday" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbol=XPD"

Sample Intraday JSON

{
"success": true,
"base": "USD",
"date": "2026-09-15",
"symbol": "XPD",
"unit": "per troy ounce",
"data": [
{ "timestamp": 1789400000, "rate": 0.000748 },
{ "timestamp": 1789410000, "rate": 0.000746 },
{ "timestamp": 1789420000, "rate": 0.000744 }
]
}

Implementation detail: Align intraday timestamps to UTC and decide on your resampling strategy (e.g., 5-min VWAP across multiple snapshots, or last-tick). Cache intraday responses carefully; do not hammer endpoints during market lulls or overnight.

Supported Symbols and discoverability

Before you scale beyond Palladium, inspect the full symbol set programmatically. This lets you expand pricing to Platinum (XPT) or Nickel (XNI) for catalyst substitution scenarios, or add Aluminum (XAL) and Copper (XCU) for chassis and electrical components.

Query supported symbols

curl -s "https://metals-api.com/symbols"

You can also browse the reference at Metals-API Supported Symbols to plan your product or risk coverage map.

Unit conversions: per troy ounce to grams, kilograms, and per-piece costs

Metals-API quotes metals per troy ounce. If your BOMs, ERP, or catalogs require grams or kilograms, convert explicitly:

  • grams_per_ounce = 31.1034768
  • kg_per_ounce = 0.0311034768
  • price_per_gram = (USD_per_ounce) / 31.1034768
  • price_per_kg = (USD_per_ounce) / 0.0311034768

Where USD_per_ounce = 1 / rate (because rate is XPD per 1 USD). If you’re multiplying by a quantity in troy ounces, you can work directly in the API’s native unit without inversion confusion. Standardize conversions into utility functions to reduce copy/paste errors across services.

Handling weekends, holidays, and market closures

Metals trading and FX markets observe closures that produce flat data or missing dates:

  • Expect fewer or no updates over weekends and holidays. Do not assume a daily record exists for every calendar date.
  • For backfilling, either forward-fill (carry the prior business day) or keep nulls; choose one rule and document it.
  • In alerts, silence or widen thresholds on known-closure dates to avoid noise.

Caching, retries, and cost control

Design your integration to be both robust and economical:

  • Cache by (endpoint + base + symbols + date-range parameters). Include timestamp in the cache payload for downstream traceability.
  • Use ETag-like strategies on your side with conservative TTLs aligned to your plan’s update cadence.
  • Retry transient network errors with jittered backoff; never tight-loop retries.
  • Batch symbols: request multiple related symbols together where supported to reduce calls.
  • Normalize and persist responses to your data store for historical reuse (warehouse, time-series DB).

Error handling and data validation

Harden your pipelines against malformed inputs and service errors:

  • Validate that success is true; otherwise, inspect error fields before proceeding.
  • Verify unit is “per troy ounce” for metals data; if unexpected, log and halt conversion-sensitive steps.
  • Sanitize symbol inputs from user-facing UIs to prevent unsupported requests.
  • On empty or partial rates, decide whether to fallback to the most recent cached rate or halt processing; document the rule per system.

Security and key management

  • Store the access_key in a secrets manager, not in source control.
  • Rotate keys periodically; build key rotation into CI/CD with safe deploy and rollback paths.
  • Restrict who can download raw data from production stores; treat pricing as sensitive.
  • Instrument audit logs for every call that affects pricing or hedging.

Architectural patterns for smart manufacturing and digital supply chains

Consider an event-driven approach for resilient distribution of XPD-ASK across your estate:

  • Polling microservice: Periodically pulls Bid/Ask and Latest for XPD (and related metals), normalizes to a canonical schema (with base, unit, timestamp), and publishes to a message bus.
  • Consumers:
    • Pricing engine updates catalog SKUs and CPQ quotes in near real time.
    • Risk service computes intraday VaR and spread exposure.
    • ERP adaptor updates purchase orders and budget utilization.
  • Data lakehouse: Stores raw and curated layers (bronze/silver/gold) for analytics and ML.

This decouples external dependencies from customer-facing latencies and keeps your retry pressure off your frontend requests.

Automotive technology and environmental implications of Palladium data

Palladium enables catalytic converters to reduce hydrocarbons, CO, and NOx. As regulatory limits tighten, demand elasticity depends on substitution (e.g., platinum) and recycling rates. Real-time and historical Palladium data become inputs into:

  • Forecasting catalyst loadings per engine type and region-specific standards.
  • Simulating CO2 credit impacts when raw material costs drive powertrain mix shifts.
  • Optimizing remanufacturing and recycling operations based on near-term price and spreads.

These datasets, delivered via Metals-API, allow automotive and industrial teams to stitch pricing signals into digital supply chains and smart manufacturing systems, improving both cost control and sustainability goals.

End-to-end example: enterprise pricing of a Palladium-bearing component

  1. Every 10 minutes (plan-dependent), poll Bid/Ask for XPD with base=USD. Extract ask, compute USD/oz = 1 / ask.
  2. Convert USD/oz to EUR/oz via Convert if your storefront is in Europe.
  3. Compute per-gram and per-piece: grams needed per assembly times EUR/gram.
  4. Blend in surcharge for logistics and quality testing; surface the final per-piece cost to CPQ.
  5. For dashboards, call Time-series overnight to refresh weekly and monthly charts.
  6. Run Fluctuation to detect if weekly change_pct exceeds risk threshold; auto-notify procurement.
  7. Archive all JSON payloads, timestamped, in an immutable store for audit.

Practical gotchas a beginner might miss

  • Base inversion: Rates are per 1 USD. Don’t forget to invert for USD per ounce if your math expects it.
  • Spread vs mid: Execution and P&L should consider bid/ask. Backtests often use mid; document the difference.
  • Troy ounces vs grams: Seamless internally, but one wrong unit constant can propagate errors everywhere. Centralize conversions.
  • Weekend gaps: Don’t fill weekends with fabricated values unless your analytics explicitly require forward-fill.
  • Date vs timestamp: Always track both; align reporting date with business calendars to avoid mislabeling.

Comparing Palladium (XPD) to Gold (XAU) in your stack

Many teams start with Gold (XAU) benchmarks and then expand to Palladium. In Metals-API, both XAU and XPD follow the same JSON structure and unit conventions. Practical differences in your implementations often come down to:

  • Volatility regimes: Palladium can exhibit different intraday behavior than Gold; tune your alert thresholds separately.
  • Demand drivers: Automotive and emissions policy strongly affect Palladium; macro and central bank flows dominate Gold.
  • Inventory hedges: Manufacturers may hedge Palladium’s embedded cost differently than Gold used in jewelry or electronics contacts.

Documentation, symbols, and getting started links

For broader market context and cross-checking methodologies, you may also consult reputable financial data and analysis resources like the London Metal Exchange and CME Group to understand how exchange microstructure and contract specs relate to spot-oriented data used in manufacturing and procurement.

Deep dive: field-by-field interpretations and downstream usage

Understanding each response field ensures clean transformations and accurate KPIs.

  • success: Boolean—always check before processing; drive error branches when false.
  • timestamp: Epoch-like number—place it in UTC columns and use it to segment caches.
  • date: YYYY-MM-DD—represent the business date; essential for joins to calendars and financial reporting.
  • base: Expect “USD” by default—log divergences if your system assumes USD.
  • rates: Object keyed by symbol—loop safely, as not every symbol you request may be returned if unsupported or unavailable for that time.
  • unit: “per troy ounce”—store as metadata or schema attribute; don’t rely on ad hoc assumptions.

Performance and scaling strategies

  • Batch symbols in a single call where possible (e.g., XPD,XPT,XAU) to reduce roundtrips.
  • Stagger polling across services to avoid thundering herds at the top of the minute.
  • Implement layered caches: per-request in-process cache, then shared cache (Redis), then persisted snapshots.
  • Use asynchronous pipelines: queue raw responses and process them in workers to protect your customer-facing latency budgets.
  • Monitor with SLOs: track availability, response latency, and staleness windows vs your plan’s update cadence.

Testing and observability

  • Create synthetic checks that verify inversion math and unit conversions using fixture responses.
  • Log request IDs, timestamps, parameters, and response sizes for later forensic analysis.
  • Alert on missing fields, unit mismatches, or unexpected base currency responses.

Troubleshooting common issues

  • Empty or partial rates:
    • Cause: Unsupported symbol, holiday, or symbol not available for the date requested.
    • Fix: Verify symbol via Supported Symbols. For historical gaps, try adjacent business dates or Time-series with a wider range.
  • Unexpected currency conversions:
    • Cause: Misinterpreting base and inversion.
    • Fix: Confirm that rates are in asset-per-USD. For USD per ounce, invert the rate. Document and unit test this logic.
  • Weekend flatlines:
    • Cause: Market closures.
    • Fix: Don’t alert on closures; schedule lower-frequency polling and relax thresholds.
  • Precision drift in cost rolls:
    • Cause: Floating-point rounding during repeated inversions and conversions.
    • Fix: Use decimal types and round only at presentation. Store high-precision base values in your database.

Security best practices for production

  • Do not expose access_key in client-side code for public apps; proxy through your backend.
  • Use least-privilege IAM on infrastructure that stores or processes pricing data.
  • Sanitize all query parameters in your proxy layer to prevent misuse or overconsumption.
  • Encrypt data at rest and in transit; apply row-level security for multi-tenant pricing databases.

Putting it all together: an implementation checklist

  • Get your API key from the Metals-API Website.
  • Design schemas that capture: base, unit, timestamp, date, symbol, bid/ask/mid, and derived USD per ounce.
  • Implement polling cadence aligned to your plan’s update interval.
  • Build a conversion utility that:
    • Inverts asset-per-USD to USD-per-asset when needed.
    • Transforms troy ounces to grams/kilograms.
    • Performs currency conversion via the Convert feature.
  • Add analytics refresh jobs using Time-series, OHLC, Fluctuation, and Lowest/Highest.
  • Harden with retries, caching, structured logging, and unit/integration tests.
  • Document operational runbooks for closures, exceptions, and reprocessing historical windows.

Complete example: curl requests and responses you can test now

Below are executable curl examples you can paste into your terminal. Replace YOUR_KEY with your access key.

1) Live Palladium Ask

curl -sG "https://metals-api.com/api/bid-ask" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "base=USD" \
--data-urlencode "symbols=XPD"
{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"rates": {
"XPD": {
"bid": 0.000742,
"ask": 0.000746,
"spread": 4.0e-6
}
},
"unit": "per troy ounce"
}

2) Latest snapshot including Palladium

curl -sG "https://metals-api.com/api/latest" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "symbols=XPD,XPT,XAU" \
--data-urlencode "base=USD"
{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"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"
}

3) Historical day for Palladium

curl -sG "https://metals-api.com/api/2026-09-14" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "symbols=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"timestamp": 1789345456,
"base": "USD",
"date": "2026-09-14",
"rates": {
"XAU": 0.000485,
"XAG": 0.03825,
"XPT": 0.000915,
"XPD": 0.000748
},
"unit": "per troy ounce"
}

4) Time-series window for Palladium

curl -sG "https://metals-api.com/api/timeseries" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "start_date=2026-09-08" \
--data-urlencode "end_date=2026-09-15" \
--data-urlencode "symbols=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"timeseries": true,
"start_date": "2026-09-08",
"end_date": "2026-09-15",
"base": "USD",
"rates": {
"2026-09-08": { "XPD": 0.000749 },
"2026-09-09": { "XPD": 0.000750 },
"2026-09-10": { "XPD": 0.000747 },
"2026-09-11": { "XPD": 0.000746 },
"2026-09-12": { "XPD": 0.000746 },
"2026-09-13": { "XPD": 0.000746 },
"2026-09-14": { "XPD": 0.000748 },
"2026-09-15": { "XPD": 0.000744 }
},
"unit": "per troy ounce"
}

5) Fluctuation for Palladium

curl -sG "https://metals-api.com/api/fluctuation" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "start_date=2026-09-08" \
--data-urlencode "end_date=2026-09-15" \
--data-urlencode "symbols=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"fluctuation": true,
"start_date": "2026-09-08",
"end_date": "2026-09-15",
"base": "USD",
"rates": {
"XPD": {
"start_rate": 0.000749,
"end_rate": 0.000744,
"change": -5.0e-6,
"change_pct": -0.67
}
},
"unit": "per troy ounce"
}

6) OHLC for Palladium

curl -sG "https://metals-api.com/api/open-high-low-close/2026-09-15" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "symbols=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"timestamp": 1789431856,
"base": "USD",
"date": "2026-09-15",
"rates": {
"XPD": {
"open": 0.000748,
"high": 0.000752,
"low": 0.000742,
"close": 0.000744
}
},
"unit": "per troy ounce"
}

7) Lowest/Highest for Palladium

curl -sG "https://metals-api.com/api/lowest-highest/2026-09-15" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "symbols=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"date": "2026-09-15",
"base": "USD",
"rates": {
"XPD": {
"lowest": 0.000742,
"highest": 0.000752
}
},
"unit": "per troy ounce"
}

8) Intraday for Palladium

curl -sG "https://metals-api.com/api/intraday" \
--data-urlencode "access_key=YOUR_KEY" \
--data-urlencode "symbol=XPD" \
--data-urlencode "base=USD"
{
"success": true,
"base": "USD",
"date": "2026-09-15",
"symbol": "XPD",
"unit": "per troy ounce",
"data": [
{ "timestamp": 1789400000, "rate": 0.000748 },
{ "timestamp": 1789410000, "rate": 0.000746 },
{ "timestamp": 1789420000, "rate": 0.000744 }
]
}

Advanced analysis techniques for developers

  • Spread decomposition: Compare Bid/Ask from multiple snapshots to measure intraday spread volatility; flag widening conditions that may affect procurement timing.
  • Cross-metal hedging: Use Time-series for XPD and XPT to model substitution risk; compute rolling correlations and hedge ratios.
  • FX overlay: Combine Convert with metal rates to maintain hedges in buyer-local currencies, reducing P&L translation noise.
  • Signal engineering: From OHLC, compute ATR-like ranges and breakout triggers for purchase orders or sales promos linked to metal costs.

Real-world case study: digital supply chain with automated alerts

A Tier-1 auto supplier integrated Metals-API to link Palladium Ask into a Kafka-backed microservice bus:

  • Every 15 minutes, pull XPD Bid/Ask and compute EUR-per-gram.
  • Publish an event with latest EUR-per-component cost for catalyst assemblies.
  • ERP auto-adjusts purchase requisitions when 7-day Fluctuation exceeds ±1%.
  • BI dashboards (OHLC + Lowest/Highest) inform treasury hedges and pricing committees.
  • Result: Faster quote turnaround, lower variance in gross margin, and improved compliance with regional emissions-related cost pass-through rules.

Conclusion

Palladium Ask (XPD-ASK) data is the connective tissue between automotive innovation, emissions compliance, and smart manufacturing economics. With Metals-API, you can retrieve live bid/ask, transform values into operational currencies, and power advanced analytics using historical, time-series, OHLC, fluctuation, and intraday datasets—all in simple, consistent JSON. If you’re building trading tools, fintech products, procurement automation, or research pipelines, Metals-API provides the foundation to price accurately, hedge intelligently, and operate with confidence. Start by getting your free key on the Metals-API Website, then dive into the Metals-API Documentation and explore coverage on the Supported Symbols page.

FAQ

  • What is the base currency for rates?
    • USD by default. Rates are asset-per-USD. Invert to get USD per troy ounce.
  • How do I get the Palladium Ask price specifically?
    • Use the Bid/Ask feature with symbols=XPD. Read rates.XPD.ask for the ask quote.
  • How do I handle troy ounces vs grams?
    • Convert with 1 troy ounce = 31.1034768 grams. Standardize this conversion centrally.
  • Do weekends affect data?
    • Yes. Expect fewer updates or gaps. Use carry-forward rules or leave nulls for analytics.
  • Can I obtain historical data?
    • Yes. Use Historical for a single date and Time-series for ranges. OHLC and Lowest/Highest provide bar-like and extreme values by date.
  • How can I convert Palladium values into EUR or JPY?
    • Derive USD value from Bid/Ask, then use Convert from USD to your target currency. Log the FX rate for audit.
  • Is spread included in Latest?
    • Latest provides indicative rates. For precise execution logic, use Bid/Ask and read bid/ask/spread explicitly.
  • Where can I find all supported symbols?
  • How do I start?

Ready to use Metals-API?

Try it now!

Search

Related Posts

Recent Posts