Silver Price is a simple tool for getting the current price of silver. It returns the current price of silver in any currency and in various units.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Silver Price response payload
}
}
About the Silver Price API
Silver Price works by analyzing the current market data and getting the current price of silver. It uses various sources to determine the current price of silver and returns the price in any currency per ounce, gram, and kilogram.
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
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Silver Price
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Silver Price API do?
How do I authenticate Silver Price API requests?
How much does the Silver Price API cost?
How fast is the Silver Price API?
What response formats does the Silver Price API support?
What HTTP method does the Silver Price API use?
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
| Parameter | Type | Example | Description |
|---|---|---|---|
currencyOptionalPremium | string | USD | The currency to get the price in default USD |
hourlyOptionalPremium | boolean | true | Include hourly price data for the past 24 hours default false |
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.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
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.
{
"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.
| Field | Type | Example | Description |
|---|---|---|---|
currency | string | "USD" | ISO 4217 currency code for price values |
gram | number | 1.58 | Silver price per gram in specified currency |
kilogram | number | 1584.07 | Silver price per kilogram in specified currency |
ounce | number | 49.27 | Silver price per troy ounce in specified currency |
lastUpdated | string | "2026-02-07T12:00:00.000Z" | ISO 8601 timestamp of last price update |
change24h | number | 0.42 | Price change vs 24 hours ago in currency units |
change24hPctPremium | number | 0.86 | Percentage price change vs 24 hours ago |
changeDirection | string | "up" | Direction of 24h change: up, down, or unchanged |
high24hPremium | number | 49.55 | Highest price in the past 24 hours |
low24hPremium | number | 48.8 | Lowest price in the past 24 hours |
formatted | object | {...} | |
ouncePremium | string | "$49.27" | Formatted ounce price with currency symbol |
gramPremium | string | "$1.58" | Formatted gram price with currency symbol |
kilogramPremium | string | "$1,584.07" | Formatted kilogram price with currency symbol |
ounceWordsPremium | string | "forty-nine dollars" | Ounce price spelled out in words with currency |
kilogramWordsPremium | string | "one thousand, five hundred eighty-four dollars" | Kilogram price spelled out in words with currency |
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.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
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.
| Plan | Per month | Credits | Silver Price calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
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.
Call it from cURL — GET /v1/silverprice
No SDK to install — this is a plain HTTPS call to /v1/silverprice with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/silverprice" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/silverprice
Install the Node.js SDK, then call the Silver Price API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/silverpriceconst res = await fetch("https://api.apiverve.com/v1/silverprice", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/silverprice
Install the Python SDK, then call the Silver Price API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-silverpriceimport requests
res = requests.get(
"https://api.apiverve.com/v1/silverprice",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/silverprice
Install the C# / .NET SDK, then call the Silver Price API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.SilverPriceusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/silverprice");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/silverprice
No SDK to install — this is a plain HTTPS call to /v1/silverprice with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/silverprice", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/silverprice
No SDK to install — this is a plain HTTPS call to /v1/silverprice with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/silverprice");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/silverprice
No SDK to install — this is a plain HTTPS call to /v1/silverprice with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/silverprice")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
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.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Silver Price API.
Finance
- Balance Sheet
- Benchmark Rate
- BIN Lookup
- Bitcoin Price
- Cash Flow Statement
- Company Lookup
- Cost of Living
- CPI Inflation
- Currency Converter
- Currency Symbols
- Dividends
- Earnings Report
- Ethereum Price
- Exchange Rate
- Financial Ratios
- GDP Data
- Global Stock Market
- Gold Price
- I-Bond Rates
- IFSC Lookup
- Income Statement
- Income Tax Brackets
- Income Tax Calculator
- Inflation Rate
- Insider Trading
- Interest Rate
- Jobs Report
- Loan Calculator
- Minimum Wage
- Mortgage Calculator
- Mortgage Rate
- National Debt
- Palladium Price
- Platinum Price
- Population Data
- Purchasing Power
- Routing Number Lookup
- Sales Tax Calculator
- Sales Tax Lookup
- Sanctions Screening
- SEC Filings
- Silver Price
- Stock Exchange
- Stock Market Open Times
- SWIFT Code Lookup
- Trade Balance
- Treasury Yields
- Unemployment Rate
- VAT Rates
Related articles
All articles →
Enrich Your CRM with Public Company DataAutomatically fill in company details for sales leads using SEC data. Ticker, industry, address, and more from a single API call.Read
Currency Conversion: Handling Exchange Rates CorrectlyExchange rates change constantly. Learn how to handle currency conversion in applications with accuracy and reliability.Read
Going Global: Building Multi-Currency AppsYour app works great in dollars. Now a customer in Germany wants to pay in euros. Here's what to know.Read