Silver Price API

About the Silver Price API

Each request returns real-time silver prices calculated per gram, kilogram, and troy ounce, defaulting to USD with a timestamp and 24-hour price change. Paid plans can switch to any of 172 supported ISO currencies, retrieve 24-hour percentage changes, or pass an hourly flag to receive 24 historical hourly price points.

What people use it for

Bullion Store Checkout

Bullion dealers calculate live retail markups against current per-ounce spot silver rates during customer checkout to prevent selling below metal value.

Scrap Metal Valuation

When customers bring in scrap sterling silverware, pawnbrokers compute melt values on the spot using real-time price per gram metrics.

Precious Metals Portfolio Tracking

Portfolio tracking apps update silver holding balances and show day-over-day price direction indicators to keep investors informed of short-term volatility.

Industrial Material Pricing

Calculate contract fabrication estimates for silver-bearing electrical contacts and solar cell pastes by querying bulk kilogram rates at quote generation.

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

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

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": 1.58,
    "kilogram": 1584.07,
    "ounce": 49.27,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "change24h": 0.42,
    "change24hPct": 0.86,
    "changeDirection": "up",
    "high24h": 49.55,
    "low24h": 48.8,
    "formatted": {
      "ounce": "$49.27",
      "gram": "$1.58",
      "kilogram": "$1,584.07",
      "ounceWords": "forty-nine dollars",
      "kilogramWords": "one thousand, five hundred eighty-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 Silver 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 — Silver 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