Platinum Price API

About the Platinum Price API

The API polls live precious metal markets and delivers spot rates across troy ounces, grams, and kilograms. By default, responses return quotes in USD with 24-hour price change amounts and directional trends. Upgrading to a paid plan lets you convert prices into 172 world currencies, view 24-hour high and low ranges, or pull 24 hours of hourly price snapshots.

What people use it for

Jewelry Inventory Valuation

When revaluing finished jewelry stock, retail catalog systems calculate replacement costs based on spot platinum prices per gram.

Bullion Checkout Rates

Bullion dealers lock in customer checkout totals by converting ounce rates into local purchase prices right before payment capture.

Scrap Metal Intake

Price scrap catalytic converters accurately by referencing live per-kilogram platinum values and day-over-day change directions during intake.

Commodities Portfolio Tracking

To monitor precious metal allocations, wealth management dashboards track spot rates and 24-hour price shifts to calculate daily asset swings.

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/platinumprice

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/platinumprice?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/platinumprice

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": 51.62,
    "kilogram": 51617.99,
    "ounce": 1605.5,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "change24h": 12.3,
    "change24hPct": 0.77,
    "changeDirection": "up",
    "high24h": 1618,
    "low24h": 1592.4,
    "formatted": {
      "ounce": "$1,605.50",
      "gram": "$51.62",
      "kilogram": "$51,617.99",
      "ounceWords": "one thousand, six hundred six dollars",
      "kilogramWords": "fifty-one thousand, six hundred eighteen 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 Platinum 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 — Platinum 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