Discover/Norges Bank API
live

Norges Bank APInorges-bank.no

Access Norges Bank's upcoming policy rate decisions, speeches, and scheduled publications via a single API endpoint with filtering and pagination support.

This API takes change requests — .
Endpoint health
verified 3h ago
get_calendar_events
1/1 passing latest checkself-healing
Endpoints
1
Updated
3h ago

What is the Norges Bank API?

The Norges Bank Calendar API exposes 1 endpoint — get_calendar_events — that returns upcoming scheduled events from Norway's central bank, including monetary policy rate decisions, speeches, and publications. Each response includes up to 10 fields per event object, a total_hits count for pagination planning, and a types array listing all available event-type filters.

This call costs1 credit / call— charged only on success
Try it
Number of events to skip from the beginning of the result set for pagination.
Maximum number of events to return. Must be between 1 and 100.
Filter events by type. When omitted, all event types are returned.
api.parse.bot/scraper/0d027f0a-a8f9-407d-b292-1ca4ab75476a/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/0d027f0a-a8f9-407d-b292-1ca4ab75476a/get_calendar_events?skip=0&limit=10&event_type=policy_rate_decisions' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace norges-bank-no-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Norges Bank Calendar API — list upcoming events, filter by type."""
from parse_apis.norges_bank_no_api import NorgesBank, EventType, InputFormatInvalid

client = NorgesBank()

# List the next few calendar events across all types.
for event in client.events.list(limit=5):
    print(event.title, "|", event.formatted_date, "|", event.event_time)

# Filter to policy rate decisions only.
try:
    decision = client.events.list(event_type=EventType.POLICY_RATE_DECISIONS, limit=1).first()
except InputFormatInvalid as e:
    print(f"Invalid request: {e.message}")
    decision = None
if decision is not None:
    print(f"Next rate decision: {decision.title} on {decision.date}")
    print(f"  URL: {decision.url}")

print("exercised: events.list (all types) / events.list (filtered)")
All endpoints · 1 totalmissing one? ·

Returns upcoming calendar events from Norges Bank. Events include policy rate decisions, speeches, and other scheduled publications. Results are ordered chronologically from the nearest future date. Supports pagination via skip/limit and optional filtering by event type. Each API call fetches up to limit results, paginating internally if needed (max 10 per upstream page).

Input
ParamTypeDescription
skipintegerNumber of events to skip from the beginning of the result set for pagination.
limitintegerMaximum number of events to return. Must be between 1 and 100.
event_typestringFilter events by type. When omitted, all event types are returned.
Response
{
  "type": "object",
  "fields": {
    "skip": "number of events skipped",
    "limit": "maximum number of events requested",
    "types": "array of available event type filters with id and name",
    "events": "array of calendar event objects",
    "total_hits": "total number of matching events available"
  },
  "sample": {
    "data": {
      "skip": 0,
      "limit": 5,
      "types": [
        {
          "id": "145879",
          "name": "Policy rate decisions"
        },
        {
          "id": "145880",
          "name": "Speeches"
        }
      ],
      "events": [
        {
          "id": 147914,
          "url": "https://www.norges-bank.no/en/news-events/calendar/policy-rate-decisions/26-09-24/",
          "date": "2026-09-24T10:00:00+02:00",
          "type": "Policy rate decisions",
          "group": "September 2026",
          "title": "Policy rate decision and Monetary Policy Report",
          "event_time": "Thursday 10:00",
          "formatted_date": "24 Sep 2026"
        }
      ],
      "total_hits": 11
    },
    "status": "success"
  }
}

About the Norges Bank API

What the API Returns

The get_calendar_events endpoint returns a chronologically ordered list of upcoming Norges Bank events. Each response contains an events array of calendar event objects, a total_hits integer indicating how many total matching events exist, a types array of available filter categories (each with an id and name), and the skip and limit values echoed back for pagination bookkeeping.

Filtering and Pagination

Pagination is handled via the skip and limit parameters. limit accepts any integer between 1 and 100. To page through results, increment skip by your page size on each request and compare cumulative records fetched against total_hits to know when results are exhausted. The optional event_type parameter accepts a filter id value from the types array returned in any prior response — passing it restricts results to one category, such as policy rate decisions or press conferences.

Coverage and Scope

Events span Norges Bank's official public calendar, covering the categories that Norges Bank publishes: monetary policy meetings, interest rate announcements, speeches by bank officials, and other scheduled publications. Events are ordered from the nearest future date forward, so the first result is always the next imminent event. The source does not expose historical events that have already passed — only forthcoming scheduled items appear in responses.

Reliability & maintenanceVerified

The Norges Bank API is a managed, monitored endpoint for norges-bank.no — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when norges-bank.no changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official norges-bank.no API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
3h ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Alert trading systems when a Norges Bank policy rate decision appears in the calendar
  • Build a financial news dashboard that surfaces upcoming NOK-relevant central bank events
  • Aggregate Nordic central bank calendars by combining this API with equivalent sources
  • Notify analysts automatically when new speeches or publications are scheduled by filtering on event_type
  • Track the full forward calendar of Norges Bank events by paginating with skip and total_hits
  • Integrate monetary policy meeting dates into backtesting pipelines for NOK currency strategies
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Norges Bank offer an official developer API?+
Norges Bank publishes some data through its official data portal at https://data.norges-bank.no, which covers exchange rates and other statistical series. The calendar data surfaced by this API is not part of that official developer offering.
What does the `types` field in the response contain?+
The types array lists every available event category on the Norges Bank calendar at the time of the request. Each entry has an id and a name. You can pass any id value as the event_type input parameter to filter subsequent calls to only that category of event.
Does the API return past Norges Bank events or only future ones?+
Only future scheduled events are returned. Results are ordered chronologically starting from the nearest upcoming date. Historical events that have already occurred are not included in responses. You can fork this API on Parse and revise it to add a historical events endpoint if that coverage is needed.
Does the API return the full text or minutes from policy decisions and speeches?+
No. The API returns calendar metadata — event type, scheduled date, and associated labels — not the text content of speeches, rate decisions, or publications. You can fork the API on Parse and revise it to add an endpoint that fetches the content of a specific event page.
How should I page through all available events?+
Set limit to your preferred page size (max 100) and increment skip by that amount on each request. The total_hits field in every response tells you the total number of matching events, so you can stop fetching once the sum of skip and items returned meets or exceeds total_hits.
Page content last updated . Spec covers 1 endpoint from norges-bank.no.