---
title: "NBP gold fixing - historical series"
method: GET
path: "/api/v1/nbp/gold/history"
tags: ["Central Banks & Monetary"]
---

# NBP gold fixing - historical series

`GET /api/v1/nbp/gold/history`

NBP gold fixings either across a date range (from/to, any length - auto-chunked at 93 days server-side) or the last N publications (last_n). Exactly one mode must be supplied. History is available from 2013-01-02.

## Query parameters

- `from` string, nullable — Start date (YYYY-MM-DD). Required with `to`.
- `to` string, nullable — End date (YYYY-MM-DD). Required with `from`.
- `last_n` integer, nullable — Return last N observations (1-255). Mutually exclusive with from/to.

## Response `200`

Gold fixings sorted by ascending date.

- EnvelopeNbpGoldHistoryPayload
  - `data` NbpGoldHistoryPayload, required — NBP gold fixings across a date range or last-N window.
    - `rows` NbpGoldRow[], required — Dated gold fixings in ascending `data` order.
      - `data` string, required — Publication date of the fixing (YYYY-MM-DD, Warsaw business day).
      - `cena` number, required — Price of 1 gram of pure gold (fineness 1000) in PLN, as calculated by NBP.
    - `count` integer, required — Number of observations returned.
  - `meta` SugraMeta, required — Metadata attached to every /api/v1/* response envelope.
    - `endpoint` string, required — Requested endpoint path.
    - `data_time` string, required — ISO 8601 UTC timestamp of the source data, not of the request.
    - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced.
    - `provider` string, required — API name and version.
    - `source` string, nullable — Identifier of the primary upstream source used for this response.
    - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response.
    - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data.
    - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried.
    - `cached` boolean, nullable — True when this response was served from the internal cache.
    - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data.

## Other responses

- `401` — Missing or invalid `x-api-key` header.
- `422` — Validation Error
- `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window.
- `503` — Upstream source is temporarily unavailable. Retry after a short delay.

---

[API](https://skmtc.net/sugra/apis/sugra-api.md) · [All operations](https://skmtc.net/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sugra/sugra-api/versions/dcf7427e6897/schema)