UBS Gold 99.99% · Commodities · 1 endpoint
UBS Gold Two-Way Quote
UBS Gold 99.99% buy and sell prices side by side, with the dealer spread calculated per bar size.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 120 / 60s
- Cache
- 5m
- Requests
- 0
Endpoint
How to call it
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/gold/ubs \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"gold-ubs","params":{"max_age":"60"}}Parameters
- max_ageinteger (seconds) · optional
- Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300
Example response
200 OK
JSON
{
"data": {
"vendor": "ubs",
"bars": [
{
"grams": 1,
"sell_idr": 2555000,
"buy_idr": 2365000,
"sell_per_gram_idr": 2555000,
"buy_per_gram_idr": 2365000,
"spread_idr": 190000,
"spread_percent": 7.44
}
]
},
"meta": {
"request_id": "req_7Q2fK4mZ",
"as_of": "2026-08-18T16:32:00.000Z",
"age_seconds": 42,
"next_update_at": "2026-08-18T17:10:15.000Z"
}
}- bars[].grams
- Bar weight in grams.
- bars[].sell_idr
- What the dealer sells the bar for.
- bars[].buy_idr
- What the dealer buys it back for.
- bars[].spread_percent
- `(sell - buy) / sell`, as a percentage. The real cost of a round trip at that size.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Data freshness
Every response is timestamped
as_of is when the data was published, age_seconds how old it is now, and next_update_at when newer data is expected.
Up to date
200
Inside its published window. Almost every request.
Delayed
delayed: true
Newer data is late; you get the latest there is, flagged.
Unavailable
503
Nothing recent enough. Carries Retry-After, never billed.
Health
Is it up?
- UBS Gold Two-Way Quote
1/1 passing