Gold Price API

About the Gold Price API

Requests retrieve real-time spot gold valuations denominated in USD across ounce, gram, and kilogram weights, accompanied by 24-hour change values and price direction. Paid tiers can query prices across 172 currency codes, retrieve 24-hour high and low ranges, and include hourly price snapshots spanning the preceding day.

What people use it for

Jewelry Store Pricing

E-commerce jewelers adjust retail bullion and custom jewelry checkout prices dynamically based on live gold rates per gram.

Portfolio Asset Valuation

Wealth tracking dashboards recalculate physical precious metal portfolio balances by multiplying recorded gold ounces against incoming spot rates.

Pawn Shop Appraisals

When customers bring in scrap scrap gold, collateral loan software pulls the latest kilogram and gram benchmarks to calculate fair lending values.

Trading Alert Triggers

Market watch bots monitor 24-hour change direction and absolute price shifts to push notifications when bullion moves significantly.

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

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/goldprice?currency=USD&hourly=true&hourly[].hour=1&hourly[].price=1&hourly[].timestamp=value" \
  -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/goldprice

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": 138.63,
    "kilogram": 138633.92,
    "ounce": 4312,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "change24h": 28.5,
    "change24hPct": 0.67,
    "changeDirection": "up",
    "high24h": 4325,
    "low24h": 4278.5,
    "formatted": {
      "ounce": "$4,312.00",
      "gram": "$138.63",
      "kilogram": "$138,633.92",
      "ounceWords": "four thousand, three hundred twelve dollars",
      "kilogramWords": "one hundred thirty-eight thousand, six hundred thirty-four 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 Gold 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 — Gold 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