Free Gold Price API (REST, JSON, PHP)

Important Notice — 27 August 2023: Our API now runs exclusively over HTTPS for enhanced security. If your integration still uses http://, update it to https:// to avoid connection issues.

Live Gold & Silver Price API — Free Tier for Websites

Add reliable, real-time gold and silver prices to your website, blog, or application. Our free tier is built for high availability and simple integration.

• Free access — no hidden charges.
• Rate limits: 30–60 requests/hour (≈ 44,640 per month, depending on plan/allocation).
• Roadmap: additional commodities (e.g., copper, oil) and broader currency coverage.

Why Choose Our API

Developer-friendly, HTTPS JSON endpoints with global coverage and a straightforward free tier.

• Free & transparent limits. Up to 30–60 requests per hour (≈ 44,640/month), clearly documented.
• Simple integration. Language-agnostic REST + JSON. Ready-to-use PHP and cURL samples (see Section 4).
• Global coverage. Gold and silver prices with multi-currency support and common units (gram, ounce, kg, tola, baht, masha, etc.).
• Karat conversions built in. 24k down to 10k with formulas/examples in the sample package.
• Caching-first pattern. Cron + DB examples to keep pages fast and stay within rate limits.
• Security baseline. HTTPS-only endpoints; keep keys server-side (never expose in client code).
• Clear activation flow. One proof email (key + site URL) records compliance; no auto-disables, fair grace periods.

Contents

1. API Registration
2. How to Pull Real-Time Quotes
   • Pulling Gold Rates Only
   • Pulling Both Gold & Silver
3. Best Practices (Cache + Cron)
4. Integration Examples (PHP + cURL)
5. Response Format & Field Reference
6. Rate Limits & Error Handling
7. Security & Compliance
8. Support & Key Status
9. Terms & Policies

1) API Registration

• Create your API key at goldpricez.com/key/registration.
  
  
• Activation: Please read the API Terms and complete the required steps. Then send one email to goldpricekg@gmail.com with your API key and website URL so we can record compliance. If you’ve completed this step, you may skip manual activation. Otherwise, activation may remain pending until we verify and update our records. For manual checks, see goldpricez.com/key/info.
  

2) How to Pull Real-Time Quotes

Download the sample PHP code: pull_gold_rates.zip (WinZip).

Authentication: send your key via header X-API-KEY: YOUR_API_KEY. Responses are JSON. Use https:// endpoints only.

curl -X GET \
  -H "X-API-KEY: YOUR_API_KEY" \
  https://goldpricez.com/api/rates/currency/usd/measure/all

# Specific currency
curl -X GET -H "X-API-KEY: YOUR_API_KEY" \
  https://goldpricez.com/api/rates/currency/gbp/measure/all

# Specific unit
curl -X GET -H "X-API-KEY: YOUR_API_KEY" \
  https://goldpricez.com/api/rates/currency/gbp/measure/gram

curl -X GET -H "X-API-KEY: YOUR_API_KEY" \
  https://goldpricez.com/api/rates/currency/usd/measure/ounce

curl -X GET \
  -H "X-API-KEY: YOUR_API_KEY" \
  https://goldpricez.com/api/rates/currency/gbp/measure/gram/metal/all

3) Best Practices (Cache + Cron)

To stay within rate limits and improve page speed, don’t call the API on every page view. Use a simple cache:

• Create a database table (e.g., goldrate). A sample SQL is included in the zip file.
• Create a script (e.g., pull_gold_rates.php) to fetch from the API and upsert into goldrate.
• Run a cron job every 1–2 minutes:

  wget -q -O - https://your-website/pull_gold_rates.php >/dev/null 2>&1
  

• Render prices to users from your database, not directly from the API.

Tip: Implement backoff on errors and respect 429 Too Many Requests responses.

4) Integration Examples (PHP + cURL)

4.1) Minimal PHP (cURL)

<?php
$endpoint = 'https://goldpricez.com/api/rates/currency/usd/measure/all';
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
  CURLOPT_HTTPHEADER     => ['X-API-KEY: ' . getenv('GOLDPRICEZ_API_KEY')],
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_TIMEOUT        => 10,
]);
$raw = curl_exec($ch);
$http = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

if ($http === 200 && $raw) {
  $data = json_decode($raw, true);
  // TODO: persist $data to DB, then render from DB in your pages
  echo number_format($data['ounce_in_gbp'] ?? 0, 2);
} else {
  // TODO: log and fallback to last cached value
  http_response_code(503);
  echo 'Service temporarily unavailable';
}

More complete samples (including SQL and helper functions) are in pull_gold_rates.zip.

5) Response Format & Field Reference

5.1) Example (Gold, GBP, all measures)

{
  "ounce_price_usd": "1251.10",
  "gmt_ounce_price_usd_updated": "19-12-2018 01:16:01 pm",
  "ounce_price_ask": "1251.10",
  "ounce_price_bid": "1250.74",
  "ounce_price_usd_today_low": "1248.41",
  "ounce_price_usd_today_high": "1251.63",
  "usd_to_gbp": "0.790239",
  "gmt_gbp_updated": "19-12-2018 09:05:00 am",
  "ounce_in_gbp": 988.6680129,

  "gram_to_ounce_formula": 0.0321,
  "gram_in_usd": 40.16031,
  "gram_in_gbp": 31.73624321409,

  "kg_to_ounce_formula": 32.1507,
  "kg_in_usd": 40223.74077,
  "kg_in_gbp": 31786.368682344,

  "grain_to_ounce_formula": 0.002,
  "grain_in_usd": 2.5022,
  "grain_in_gbp": 1.9773360258,

  "tael-hongkong_to_ounce_formula": 1.21528,
  "tael-hongkong_in_usd": 1520.436808,
  "tael-hongkong_in_gbp": 1201.5084627171,

  "tael-japan_to_ounce_formula": 1.2056,
  "tael-japan_in_usd": 1508.32616,
  "tael-japan_in_gbp": 1191.9381563522,

  "tola-india_to_ounce_formula": 0.375,
  "tola-india_in_usd": 469.1625,
  "tola-india_in_gbp": 370.7505048375,

  "tola-pakistan_to_ounce_formula": 0.40125,
  "tola-pakistan_in_usd": 502.003875,
  "tola-pakistan_in_gbp": 396.70304017612,

  "masha_to_ounce_formula": 0.03119,
  "masha_in_usd": 39.021809,
  "masha_in_gbp": 30.836555322351,

  "ratti_to_ounce_formula": 0.00585,
  "ratti_in_usd": 7.318935,
  "ratti_in_gbp": 5.783707875465
}

5.2) Example (Gold + Silver, GBP, gram)

{
  "ounce_price_usd": "1674.47",
  "gmt_ounce_price_usd_updated": "08-03-2020 04:52:01 am",
  "ounce_price_ask": "1674.47",
  "ounce_price_bid": "1673.90",
  "ounce_price_usd_today_low": "1642.13",
  "ounce_price_usd_today_high": "1692.46",
  "usd_to_gbp": "0.766342",
  "gmt_gbp_updated": "08-03-2020 12:05:16 am",
  "ounce_in_gbp": 1283.21668874,

  "gram_to_ounce_formula": 0.0321,
  "gram_in_usd": 53.750487,
  "gram_in_gbp": 41.191255708554,

  "silver_gram_in_usd": 0.5569029,
  "silver_gram_in_gbp": 0.4267780821918,
  "silver_ounce_in_gbp": 13.295267358,
  "silver_ounce_price_ask_gbp": 13.314425908,
  "silver_ounce_price_bid_gbp": 13.276108808,
  "silver_ounce_price_gbp_today_low": 13.047738892,
  "silver_ounce_price_gbp_today_high": 13.486086516
}

5.3) Field Descriptions (Gold)

5.4) Additional Silver Fields (when metal=all)

• silver_ounce_price_usd — Silver ounce in USD
• silver_gram_in_usd, silver_gram_in_gbp — Silver gram price
• silver_ounce_in_gbp — Silver ounce in GBP
• silver_ounce_price_ask_gbp, silver_ounce_price_bid_gbp
• silver_ounce_price_gbp_today_low / _high

6) Rate Limits & Error Handling

• Free tier: 30–60 requests/hour (plan-dependent). Do not exceed limits.
• On sustained violations, IP access may be blocked.
• Recommended polling interval: 60–120 seconds via cron + DB cache.

Status Codes

• 200 OK — Successful response
• 400 Bad Request — Invalid parameters
• 401 Unauthorized — Missing/invalid X-API-KEY
• 403 Forbidden — Key not active or blocked
• 404 Not Found — Resource or path invalid
• 429 Too Many Requests — Slow down; implement backoff
• 5xx Server errors — Retry with exponential backoff

Error Payload (example)

{
  "error": true,
  "code": 429,
  "message": "Too Many Requests. Please reduce frequency."
}

7) Security & Compliance

• Use HTTPS only. Never expose your key in client-side code.
• Keep keys in server env variables; rotate if compromised.
• Cache results; avoid exposing raw endpoints directly to browsers.

8) Support & Key Status

• Email: goldpricekg@gmail.com
• Key status & trial end-date: goldpricez.com/key/info

Version: Nov 15, 2025 • Effective: Dec 06, 2025

We may update these Terms from time to time. For material changes, we’ll make reasonable efforts to provide notice (on this page, the API docs, the key status page, and/or by email to registered users). Your continued use of the API on or after the Effective Date constitutes acceptance of the updated Terms.