Guernsey Pound (GGP) - N/A Spot Price — API endpoint reference for developers

You need to price, settle, or report values in Guernsey pounds (GGP) in real time. By the end of this guide you will fetch the latest GGP spot rate from Metals-API, understand exactly what the returned fields mean, and reliably convert between USD and GGP in your code without surprises on weekends or during market pauses.

What “GGP spot” means here and the concrete use case

Metals-API delivers currency quotes alongside precious and industrial metals. For Guernsey Pound (GGP), the “spot” value you’ll query is the current exchange rate relative to the API’s base (USD by default). Typical use cases include:

• Displaying a checkout total or settlement amount in GGP while your system’s base is USD.
• Converting portfolio or P&L figures from USD to GGP for reporting.
• Normalizing historical valuation series stored in USD into GGP on demand.

This article sticks to the essentials you need to ship: using the Latest endpoint for GGP, reading the response, inverting rates correctly, and operational tips (timestamps, caching, weekends).

Endpoints to use for Guernsey Pound (GGP)

We’ll focus on two endpoints that directly support this workflow. For the broader feature set (historical, bid/ask, OHLC, etc.), see the Documentation.

• Latest Rates: returns the most recent rates with base=USD by default, including GGP.
• Convert: converts a specific amount between currencies using the current rate.

Before you code, confirm that GGP is available in your plan and spelled exactly as supported on the Symbols page.

Get the latest GGP rate

To retrieve the GGP spot rate relative to USD, call the Latest endpoint and request the GGP symbols. When the base is USD, the returned “rates.GGP” field is GGP per 1 USD. The “rates.USDGGP” field is the inverted quote: USD per 1 GGP.

curl request

curl "https://metals-api.com/api/latest?access_key=YOUR_API_KEY&symbols=GGP,USDGGP"

Sample JSON response (real sample)

{"success":true,"timestamp":1792109460,"date":"2026-10-16","base":"USD","rates":{"GGP":0.76043,"USD":1,"USDGGP":1.3150454348197729}}

How to read this response

• success: true indicates the request succeeded.
• timestamp: 1792109460 is a UNIX timestamp (seconds since epoch). Use it for caching and time alignment.
• date: "2026-10-16" is the calendar date of the quote. Aligns with the timestamp’s trading day.
• base: "USD" means all rates are expressed relative to 1 USD.
• rates.GGP: 0.76043 is GGP per 1 USD (i.e., 1 USD = 0.76043 GGP).
• rates.USDGGP: 1.3150454348197729 is USD per 1 GGP (i.e., 1 GGP = 1.3150454348197729 USD).
• rates.USD: provided as 1 for clarity since base is USD.

Symbol meanings at a glance

Code you can paste: fetch and convert USD ⇄ GGP

The following Python example calls the same Latest endpoint, extracts the GGP and USDGGP quotes, and converts a USD-denominated price into GGP.

import os
import time
import requests

API_KEY = os.getenv("METALS_API_KEY", "YOUR_API_KEY")
URL = "https://metals-api.com/api/latest"

params = {
"access_key": API_KEY,
"symbols": "GGP,USDGGP"
}

r = requests.get(URL, params=params, timeout=10)
r.raise_for_status()
data = r.json()

if not data.get("success"):
raise RuntimeError(f"API error: {data}")

timestamp = data["timestamp"] # UNIX seconds
quote_date = data["date"] # YYYY-MM-DD
base = data["base"] # Expected: "USD"
ggp_per_usd = data["rates"]["GGP"]
usd_per_ggp = data["rates"]["USDGGP"]

# Example conversions
usd_amount = 1500.00
ggp_amount = usd_amount * ggp_per_usd

ggp_invoice = 2000.00
usd_settlement = ggp_invoice * usd_per_ggp

print(f"As of {quote_date} (ts={timestamp}), base={base}")
print(f"1 USD = {ggp_per_usd} GGP; 1 GGP = {usd_per_ggp} USD")
print(f"{usd_amount} USD -> {ggp_amount:.2f} GGP")
print(f"{ggp_invoice} GGP -> {usd_settlement:.2f} USD")

Notes:

• Always prefer the direct field the API already provides. If you requested USDGGP, don’t re-invert GGP—use the provided USDGGP value to avoid floating-point drift.
• Use the timestamp to cache responses and to align conversions to a specific valuation time.
• If you need to convert a list of items where prices must be identical within a session or checkout, cache the rate for that session duration.

Converting specific amounts with the Convert endpoint

If you want Metals-API to perform the calculation server-side (rather than multiplying locally), you can use the Convert endpoint to convert between USD and GGP for a fixed amount. This can be useful for auditability in back-office integrations. For parameters and response format, see the Documentation.

Operational details developers should know

1) Base currency and inversion

• By default, base is USD. That means rates are expressed “per USD.”
• For GGP, you often want both directions. Request both GGP and USDGGP to avoid manual inversion errors in code.
• If you only requested GGP but need USD per GGP, compute it as 1.0 / rates.GGP. Prefer the directly supplied USDGGP if available.

2) Time handling

• timestamp is UNIX seconds. Store it as an integer for precise deduplication and cache keys.
• date is a calendar date (YYYY-MM-DD). Use it for reporting and end-user UI labels.
• If you aggregate values to daily bars, align by date and keep the original timestamp for traceability.

3) Updates, caching, and request economy

• The Latest endpoint refresh frequency depends on your plan. Cache responses until the next scheduled update in your plan, or a minimum of a few seconds to avoid hammering your own infrastructure.
• Session-level caching is recommended for e-commerce checkouts and quotes to keep totals consistent across screens and prevent mid-process rate changes.
• In batch or ETL jobs, pin to a timestamp or date so the entire batch uses a single coherent rate snapshot.

4) Weekends, holidays, and market hours

• FX markets generally operate 24/5. On weekends and certain holidays, the latest rate will typically remain the last available business day’s close until trading resumes.
• For deterministic results across weekend operations, explicitly store and reuse the last observed rate plus the timestamp in your database or cache.

5) Units: currencies vs. metals

• Currency pairs like GGP and USDGGP are unitless exchange rates.
• Metal quotes use “per troy ounce.” If you later blend currency conversion with metal pricing, keep the unit boundaries clear: first normalize the currency (USD ⇄ GGP), then apply any metal weight conversions separately.

6) Error handling and fallbacks

• Check success before using rates. If false, inspect the payload and log it for debugging.
• When the API is momentarily unreachable, fall back to the most recent cached rate and surface the timestamp to users (e.g., “last updated at …”).
• Validate presence of both GGP and USDGGP before rendering UI or committing a settlement. Fail fast and retry if missing.

Integrating GGP into pricing and reporting flows

Real-time checkout or quoting

• On quote open, fetch Latest with symbols=GGP,USDGGP. Store rates, date, and timestamp in session.
• Convert line items in code (prefer direct multiplication, not server round-trips) for responsiveness.
• Display a “last updated” indicator derived from timestamp and mask tiny rounding differences with a consistent decimal format across the app.

Back-office settlement

• For audit-ready conversions, you can record: source currency amount, rate field used (GGP or USDGGP), the exact timestamp/date, and a hash of the response JSON.
• For end-of-day processes, store one canonical snapshot per day as the “official” valuation for that date to avoid drift if rates refresh intraday in your plan.

Historical normalization

If you later need historical GGP rates (e.g., to rebase USD time series into GGP), consult the Historical or Time-Series endpoints in the Documentation. Keep the same inversion logic: request GGP and/or USDGGP and apply conversions consistently.

Data hygiene: precision, rounding, and formatting

• Work internally in decimals or integers (e.g., minor units) to avoid float rounding errors. Convert to formatted strings only for display.
• When presenting totals to users, keep a consistent number of fraction digits (e.g., 2 for typical fiat amounts) unless local GGP rules differ in your compliance framework.
• If you must cross-check, reconcile USD ⇄ GGP using both fields: rates.GGP × rates.USDGGP should be near 1 within rounding tolerance.

Developer tips that save time

• Request only the symbols you need (GGP, USDGGP) to minimize payload size and speed up parsing.
• Pin dependencies and alert on schema changes by validating the presence and type of keys you rely on.
• Include the raw JSON in logs with the timestamp and your request ID for post-incident analysis.
• Build a tiny helper: get_latest_fx("GGP") that returns both ggp_per_usd and usd_per_ggp along with timestamp and date. Centralize conversion math there.

Where to find symbols and docs, and how to get an API key

• Confirm symbol availability and spelling on the Symbols page.
• Review parameters, authentication, and additional endpoints in the Documentation.
• Create your key here (no free trial; plans vary by update frequency and features): Register. For managed connectivity or enterprise needs, see MCP.

GGP in broader fintech and analytics stacks

Many teams combine USD⇄GGP conversion with metals exposure, pricing, and hedging. If you later layer metals data on top, keep the dimensions separate in code: currency normalization first (USD↔GGP via Latest or Convert), then instrument pricing, then any unit conversions (e.g., troy ounces to grams) as a final step in the chain. This keeps each step testable and prevents hidden unit mix-ups.

If you benchmark or reconcile against public sources, you might also consult external references:

• Bank of England reference rates for general FX context.
• Guernsey Pound overview for background and naming conventions.

FAQ

• How do I get the USD per GGP quote? Request the USDGGP symbol with the Latest endpoint. That field is USD per 1 GGP. If you only have GGP (GGP per USD), compute USDGGP = 1 / GGP.
• Why do I see both GGP and USDGGP? They are reciprocals in a USD-based quote system. Requesting both avoids manual inversion and rounding differences across microservices.
• How often do GGP rates update? Update frequency depends on your plan’s refresh interval. Use the timestamp field for precise timing and implement caching keyed by that timestamp.
• What happens on weekends or holidays? The most recent business day’s rate typically persists until markets reopen. Cache the last good rate and display the timestamp in your UI.
• Can I convert a specific amount server-side? Yes, use the Convert endpoint to convert exact amounts between USD and GGP. See parameters in the Documentation.

Ready to integrate GGP into your pricing, settlement or research workflows? Get your API key in minutes at Register, confirm symbol details on Symbols, and use the Documentation to add conversions with a single endpoint call. For enterprise connectivity and controls, check out MCP. Note: there is no free trial; for example, Copper Monthly is $19.99/mo.