Palladium Price API

About the Palladium Price API

The endpoint returns live palladium market quotes in USD by default, calculating rates across troy ounces, grams, and kilograms. Each response includes the net 24-hour price change, direction, and last-updated timestamp. Upgrading to a paid plan lets you request prices in 172 international currencies and fetch 24-hour price extremes or hourly historical snapshots.

What people use it for

Scrap Converter Pricing

To calculate fair scrap payouts, auto recyclers pull real-time per-gram palladium rates before bidding on spent catalytic converters.

Bullion Dealer Dashboards

Precious metals brokerages update retail storefronts with live spot prices per troy ounce and display 24-hour change directions.

Industrial Procurement Alerts

When ordering raw alloy stock, manufacturing supply software flags price swings by comparing current spot rates against 24-hour changes.

Jewelry Asset Accounting

Calculate the market value of workshop inventory by multiplying recorded palladium weights in grams against incoming price feeds.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/palladiumprice

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Optional

1
2

curl "https://api.apiverve.com/v1/palladiumprice?currency=USD&hourly=true" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/palladiumprice

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

{
  "status": "ok",
  "error": null,
  "data": {
    "currency": "USD",
    "gram": 40.08,
    "kilogram": 40075.88,
    "ounce": 1246.5,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "change24h": -8.2,
    "change24hPct": -0.65,
    "changeDirection": "down",
    "high24h": 1259,
    "low24h": 1241.1,
    "formatted": {
      "ounce": "$1,246.50",
      "gram": "$40.08",
      "kilogram": "$40,075.88",
      "ounceWords": "one thousand, two hundred forty-seven dollars",
      "kilogramWords": "forty thousand, seventy-six dollars"
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Palladium Price form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Palladium Price API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1Data refreshed realtime