GETTING STARTEDIntroductionOverview of the xauapi data APIGETTING STARTEDQuickstartCreate a key and make your first requestGETTING STARTEDAuthenticationBearer tokens, key rotation and revocationGETTING STARTEDMCP integrationConnect AI tools to gold market data · Proposed integrationCONCEPTSBroker feedsBrokers and source identityCONCEPTSFreshness & coverageTimestamps, sampling and stale dataAPI REFERENCELatest quoteGET /v1/quote · Bid, Ask and spreadAPI REFERENCECandlesGET /v1/candles · M1, M5 and M15 OHLCAPI REFERENCEFeed statusGET /v1/status · Connection and freshnessRESOURCESErrors401, 429 and 503 response handlingRESOURCESUsage & limitsAnnual allowance, rate limits and billing

11 topics. Select a result to open it.

api reference

Feed status

GET /v1/status · Connection and freshness

Draft reference · Examples use sample data.

Request

GET/v1/statusBearer token

Read-only endpoint. The base URL is a placeholder; these requests are not executable yet.

Request example
curl 'https://API_BASE_URL/v1/status?feed=justmarkets' \
  -H 'Authorization: Bearer YOUR_API_KEY'

Query parameters

ParameterTypeAccepted value
feedstring · requiredjustmarkets

Pagination, date-range filters and batch size are not specified in this API contract.

Example response

200 OK Fixed sample data; not an executable market price.

application/json
{
  "demo": true,
  "feed": "justmarkets",
  "symbol": "XAUUSD",
  "timestamp": "2026-10-06T08:30:00Z",
  "sampled": true,
  "source": "JustMarkets MT5",
  "connected": true,
  "stale": false,
  "note": "Illustrative feed state, not a connection test"
}

Response fields

FieldTypeDescription
demobooleanTrue for sample responses.
feedstringIdentifies the broker connection.
symbolstringClient-facing symbol: XAUUSD.
timestampstringISO 8601 UTC source timestamp. Fixed in examples.
sampledbooleanTrue: observations may omit intermediate ticks.
sourcestringBroker platform label.
connectedbooleanIllustrative connection state in the sample.
stalebooleanWhether the observed feed is stale.
notestringAdditional context about the reported state.

Behavior & errors

A successful status response may report connected: false and stale: true. Inspect these fields even when HTTP status is 200.

All endpoints may report invalid credentials (401), a rate limit (429), or an exhausted allowance (429). See error handling →

Try scenarios in the explorer →