National Bank of Poland Pricing: Exchange Rates (2026)

Pricing overview

The National Bank of Poland (NBP) provides its API and data services without any direct financial cost to users. This means developers, researchers, and applications can access official Polish exchange rates, gold prices, and related economic data through the NBP API free of charge. The NBP's approach aligns with a public service mandate, offering open access to financial information relevant to the Polish economy. Users are encouraged to consult the NBP official data documentation for detailed information on data availability and usage terms.

There are no subscription fees, per-request charges, or tiered pricing models. Access to current and historical data for various currency tables (A, B, C) and gold prices is included. The primary considerations for users are adherence to any implicit or explicit rate limits and ensuring their use cases align with the NBP's terms of service, which typically emphasize non-commercial use or appropriate attribution for public data.

Plans and tiers

The National Bank of Poland does not operate a tiered pricing model or offer different plans for its API access. All functionality and data available through the NBP API endpoint are provided to all users under a single, unified access model. This contrasts with many commercial API providers that use tiers based on usage volume, feature sets, or support levels.

Instead of distinct plans, the NBP provides a consistent API interface for:

• Current Exchange Rates: Access to the latest official exchange rates from tables A, B, and C.
• Historical Exchange Rates: Retrieval of past exchange rate data for specific dates or date ranges.
• Gold Prices: Daily official gold prices in PLN.

Users are expected to manage their query frequency to avoid overloading the NBP servers, though specific rate limits are not publicly documented in a granular fashion. The absence of explicit tiers simplifies integration for developers, as they do not need to consider cost implications tied to scaling their API usage.

Free tier and limits

The entire National Bank of Poland API constitutes a free tier, as all access is provided without charge. There is no separate paid tier or premium offering. This comprehensive free access includes:

• Access to daily average exchange rates for major currencies (Table A).
• Access to specific exchange rates for non-convertible currencies (Table B).
• Access to buying and selling rates for selected currencies (Table C).
• Historical data for all tables, allowing for time-series analysis.
• Daily official gold prices.

While the NBP does not publicly disclose specific, hard rate limits in terms of requests per second or per day, users are generally expected to use the API responsibly. Excessive querying or attempts to scrape data at very high frequencies may result in temporary IP blocking. Best practices for API usage, such as caching data where appropriate and spacing out requests, are recommended to ensure continuous access. For example, similar public data providers sometimes recommend delays between requests (e.g., web API best practices often suggest managing request frequency).

Developers should design their applications to implement error handling for potential rate limiting responses, even if such limits are not explicitly published. This ensures robustness in case the NBP implements or enforces dynamic throttling based on server load.

Real-world cost examples

Given that the National Bank of Poland API is entirely free, all real-world usage scenarios incur zero direct costs from the NBP itself. The primary costs associated with using the NBP API would be indirect, stemming from development efforts, infrastructure to host applications consuming the API, and network transfer fees from the user's service provider.

Here are several hypothetical usage scenarios and their direct cost implications from the NBP:

• Scenario 1: Personal Finance Application

  • Description: A developer builds a mobile application that tracks personal spending in PLN but allows users to view historical conversions for transactions made in foreign currencies. The app fetches daily exchange rates from NBP for 10 different currencies.
  • NBP API Cost: $0.00
  • Indirect Costs: Costs associated with app development, server hosting (e.g., AWS Free Tier or other cloud providers), and user data storage.

• Scenario 2: Academic Research Project

  • Description: A university researcher downloads historical daily exchange rates for PLN against EUR, USD, and GBP for the past 10 years to analyze currency fluctuations. This involves several hundred API requests.
  • NBP API Cost: $0.00
  • Indirect Costs: Computing resources for data analysis, researcher's time.

• Scenario 3: Small Business E-commerce Site

  • Description: A Polish e-commerce site displays prices in both PLN and EUR, updating the EUR conversion rate daily using the NBP API. The site performs one API call per day to get the latest EUR/PLN rate.
  • NBP API Cost: $0.00
  • Indirect Costs: Website hosting, development of the currency conversion feature, ongoing maintenance.

• Scenario 4: Financial News Portal

  • Description: A financial news website includes a widget showing current NBP exchange rates for a dozen key currencies, refreshing every hour. This results in approximately 288 API calls per day.
  • NBP API Cost: $0.00
  • Indirect Costs: Website infrastructure, content management system costs, developer time for integration.

In all these examples, the direct cost for accessing the National Bank of Poland's data remains consistently zero, highlighting its value as a free public resource for official Polish financial data.

How the pricing compares

The National Bank of Poland's API stands out due to its complete lack of direct cost. This free model provides a significant advantage when compared to commercial alternatives that typically employ tiered pricing structures based on usage, features, and support.

Comparison Table: National Bank of Poland vs. Alternatives

While commercial providers like ExchangeRate-API and Open Exchange Rates offer broader currency coverage, higher request limits, and faster update frequencies (often real-time), these come with associated costs. Their free tiers are typically limited in request volume and update frequency, necessitating paid subscriptions for more intensive use cases. For example, Stripe's payment API, while not a direct currency data provider, also uses a per-transaction pricing model, illustrating typical commercial API cost structures.

The National Bank of Poland's API is specifically authoritative for Polish currency data and gold prices. Its free nature makes it an ideal choice for projects where official Polish data is paramount and budget is a constraint, or where the required data volume falls within reasonable public service usage patterns. For broader international currency data or very high-volume, low-latency requirements, commercial services become competitive options despite their costs.