Palladium Price API

About the Palladium Price API

Palladium Price returns live palladium market quotes in USD by default, priced per troy ounce, per gram and per kilogram. Use it for today's palladium price per troy ounce (oz), per gram or per kilogram, with the change over the last 24 hours, its direction, the time of the last update and whether the spot market is currently open.

Prices refresh every hour, which fits bullion and jewelry store price boards, scrap and recycling calculators, portfolio trackers and commodity dashboards that need a current palladium spot price without a market data contract.

The Free plan returns USD prices with the 24-hour change. Paid plans can price in other currencies, add the 24-hour percent change, high and low, and hourly snapshots for the past day. The last 30 daily closes are stored too: paid plans get the 7- and 30-day change and the 30-day high, low, average and volatility, and daily=true returns the closes themselves, along with prices formatted with currency symbols and in words.

How it works

A collector reads the palladium spot price from public bullion price sources every hour, trying each in turn and falling back when one fails. It stores the price per troy ounce, gram and kilogram (31.1035 grams to the ounce), a 24-slot ring of hourly snapshots and one closing price per day for the last 30 days.

change24h compares the current ounce price with a snapshot taken between 21 and 25 hours earlier, picking the one closest to 24 hours; if none exists the change fields are omitted. high24h and low24h span all snapshots from the last 25 hours, so older slots that a failed refresh left behind are ignored. hourly=true returns those snapshots sorted by time, each tagged with the UTC hour slot it was captured in.

currency (paid) converts with the stored exchange rates, and an unknown code returns a 400. Daily closes in the 30-day history are converted at each day's own exchange rate where one is stored. change7d and change30d are null until a close from that far back exists; volatility30d is the standard deviation of daily percent changes, not annualized.

marketStatus follows regular spot hours, Sunday 18:00 to Friday 17:00 New York time with a daily 17:00 to 18:00 break, and does not model exchange holidays. In the formatted block, ounceWords and kilogramWords spell the rounded price out in words.

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.

Without writing code

Gold and silver prices on DigestYourFinances compares the metals and the gold-silver ratio.

The Precious Metals widget from WidgetSpark keeps the prices on your desktop.

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&daily=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
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154

{
  "status": "ok",
  "error": null,
  "data": {
    "currency": "USD",
    "gram": 33.47,
    "kilogram": 33466.63,
    "ounce": 1040.93,
    "lastUpdated": "2026-10-27T12:00:00.000Z",
    "change24h": -11.29,
    "change24hPct": -1.07,
    "changeDirection": "down",
    "high24h": 1052.22,
    "low24h": 1040.93,
    "change7d": -63.98,
    "change7dPct": -5.79,
    "change30d": -229.07,
    "change30dPct": -18.04,
    "high30d": 1235.1,
    "low30d": 1040.93,
    "average30d": 1135.83,
    "volatility30d": 1.4294,
    "daily": [
      {
        "date": "2026-09-28",
        "price": 1235.1
      },
      {
        "date": "2026-09-29",
        "price": 1208.34
      },
      {
        "date": "2026-09-30",
        "price": 1224.27
      },
      {
        "date": "2026-10-01",
        "price": 1218.02
      },
      {
        "date": "2026-10-02",
        "price": 1187.55
      },
      {
        "date": "2026-10-03",
        "price": 1172.5
      },
      {
        "date": "2026-10-04",
        "price": 1172.49
      },
      {
        "date": "2026-10-05",
        "price": 1169.52
      },
      {
        "date": "2026-10-06",
        "price": 1166.94
      },
      {
        "date": "2026-10-07",
        "price": 1159.57
      },
      {
        "date": "2026-10-08",
        "price": 1142.54
      },
      {
        "date": "2026-10-09",
        "price": 1159.97
      },
      {
        "date": "2026-10-10",
        "price": 1151.5
      },
      {
        "date": "2026-10-11",
        "price": 1151.49
      },
      {
        "date": "2026-10-12",
        "price": 1155.39
      },
      {
        "date": "2026-10-13",
        "price": 1145.38
      },
      {
        "date": "2026-10-14",
        "price": 1134.16
      },
      {
        "date": "2026-10-15",
        "price": 1108.24
      },
      {
        "date": "2026-10-16",
        "price": 1146.93
      },
      {
        "date": "2026-10-17",
        "price": 1115.49
      },
      {
        "date": "2026-10-18",
        "price": 1115.5
      },
      {
        "date": "2026-10-19",
        "price": 1133.25
      },
      {
        "date": "2026-10-20",
        "price": 1104.91
      },
      {
        "date": "2026-10-21",
        "price": 1092.86
      },
      {
        "date": "2026-10-22",
        "price": 1063.17
      },
      {
        "date": "2026-10-23",
        "price": 1053.78
      },
      {
        "date": "2026-10-24",
        "price": 1046.49
      },
      {
        "date": "2026-10-25",
        "price": 1046.5
      },
      {
        "date": "2026-10-26",
        "price": 1052.22
      },
      {
        "date": "2026-10-27",
        "price": 1040.93
      }
    ],
    "marketStatus": "open",
    "formatted": {
      "ounce": "$1,040.93",
      "gram": "$33.47",
      "kilogram": "$33,466.63",
      "ounceWords": "one thousand, forty-one dollars",
      "kilogramWords": "thirty-three thousand, four hundred sixty-seven 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