Source-labelled market dataSource, observation time and freshness are shown with every quoteData statusAll pages
GoldObserve

API

GoldObserve Application Data Interface

Use GoldObserve read-only market, history, macro and CFTC JSON endpoints with documented parameters, freshness states, error behavior and rights limits.

APPLICATION DATA CONTRACT

Read-only evidence endpoints used by the web application

GoldObserve exposes JSON references for market, history, macro and CFTC views. These endpoints are informational interfaces: they are not executable quotes, order-routing services, bulk data feeds or a guaranteed commercial API. A successful response keeps the provider, observation time and delivery state with the values.

ENDPOINT DIRECTORY

Choose the narrowest route for the evidence you need

Current public GET routes and their documented query boundaries.
RouteParametersPurposeReuse boundary
/api/marketmetal=XAU|XAG|XPT|XPD; currency=ISO 4217; unit=oz|g|kgOne source-labelled metal quote with provider and observation time.Same-origin page delivery; provider rows are not licensed as a bulk feed.
/api/market/overviewcurrency=USD|EUR|GBP|CNY|INR; unit=oz|g|kgCoordinated gold, silver, ratio and selected local-currency references.Same-origin page delivery; provider rows are not licensed as a bulk feed.
/api/historymetal=XAU|XAG; currency; unit; range; optional detail=dailySource-labelled intraday, daily or licensed monthly history with fallback evidence.Inspect source fields: provider history is display-only; source-cleared monthly data keeps its own licence.
/api/macroseries=DCOILWTICO|DFII10|DTWEXBGS|CPIAUCSL|CPIAUCSL_YOY|M2SL|WALCL; range=1M|3M|6M|YTD|1Y|3Y|5YOfficial macro observations with revision and vintage-policy fields.Underlying official-source terms and attribution continue to apply.
/api/cotrange=1Y|3Y|5Y|10Y|MAXCFTC gold futures-only positioning with live or versioned-baseline status.CFTC public-domain acknowledgement and GoldObserve calculation labels apply.

REQUEST EXAMPLES

Examples are ordinary same-origin GET requests

Responses use JSON. Browser and intermediary caching can apply; inspect the response's cache-control, provider, observation time, stale flag and data-mode fields instead of assuming every HTTP 200 is a newly published observation.

RESPONSE CONTRACT

Official observations and GoldObserve calculations remain distinguishable

200Validated JSON; inspect source and freshness fields
400Unsupported parameter, series, range, currency or unit
503Provider and eligible fallback unavailable; no invented value
FallbackMarked server cache or verified baseline with snapshot evidence

Derived fields—such as unit conversion, matched-date offsets, net CFTC positions or year-over-year changes—are calculated by GoldObserve and should not be attributed to the upstream publisher as official values.

OPERATIONAL AND RIGHTS LIMITS

Publicly reachable does not mean licensed for unrestricted redistribution

  • No availability, latency, completeness or commercial support SLA is offered.
  • Provider terms, attribution, fair-use limits and data rights continue to apply.
  • Reachable JSON is not an invitation to archive, proxy, scrape or redistribute provider rows.
  • Do not use these references for automated trading or safety-critical decisions.
  • Version-sensitive integrations should store the response schema and source evidence they consumed.

Review data sources and provider status or read the normalization and fallback methodology.