Is the data identical to Nager.Date?

Yes, it is loaded from Nager.Date under its MIT licence. The API adds regional scope flags, the computed endpoints and the ability to query by date without downloading a whole year.

How often is it updated?

Annually, adding the next year; 2020 to 2028 are available now.

Why pay for open data?

You pay for a database you can rely on, computed endpoints, a key with a plan behind it and support, not for the data itself, which stays open.

A Nager.Date alternative with the same holiday data, a key and long weekends

Nager.Date is the open-source project the Public Holidays API is built on, and its public endpoint is free with no key and, by its own statement, no rate limits. That is a fine choice for a hobby project. Teams that ship products tend to want a database they control, a contract with a vendor, computed answers and a support address. The Public Holidays API keeps the Nager.Date route shapes so switching is a host change, adds is-it-a-holiday, next holidays and long weekends, and serves 2020 to 2028 from its own database.

Open the Public Holidays API page Nager.Date ↗

What	Nager.Date	Public Holidays API
Free tier	Free, no key, no rate limits stated (as published).	500 tokens a month, no card; one call costs 1 token.
Entry paid price	No paid plans shown (as published).	Starter $6.99 for 25,000 tokens across all 128 APIs.
Endpoints	Holidays by country and year, e.g. /api/v4/Holidays/AT/2026 (as published).	The same by-year route, plus today, next, long weekends, countries and sources.
Licence	Open-source project; the licence name is not stated on the page read.	Nager.Date public holiday data (MIT licence), loaded into the API's own database.
Support	Not stated.	Email support on paid plans and a daily automated health check of every endpoint.

Facts about Nager.Date were read from its own pages on October 29, 2026. If something has changed since, tell us and we will update the page. Sources: Nager.Date API page.

Reasons to pick Public Holidays API

Drop-in: the legacy routes return the same array shape as Nager.Date, so existing code only changes its host.
Computed endpoints that Nager.Date does not offer: is-it-a-holiday for any date, next N holidays, and long weekends per country and year.
A key, a plan and a support contact, which is what procurement asks about when a hobby integration becomes a product feature.
One key opens 127 other APIs, including the Trading Calendar for market holidays.

When Nager.Date is still the better choice

Your use is personal or non-critical and the free public endpoint is enough.
You contribute holiday corrections upstream and want the newest edit immediately.

Try it with your key

The first endpoint of the API as a curl command. Create a free key and paste it in. (Country Holidays By Year, 1 token).

curl "https://public-holidays.dataandapis.com/v1/holidays/US/2026" \
  -H "X-Api-Key: YOUR_API_KEY"

Plans

Free 500 tokens a month · Starter $6.99 for 25,000 · Pro $24.99 for 150,000 · Ultra $99.99 for 1,000,000. Every plan covers every API.

Questions people ask

Is the data identical to Nager.Date?: Yes, it is loaded from Nager.Date under its MIT licence. The API adds regional scope flags, the computed endpoints and the ability to query by date without downloading a whole year.
How often is it updated?: Annually, adding the next year; 2020 to 2028 are available now.
Why pay for open data?: You pay for a database you can rely on, computed endpoints, a key with a plan behind it and support, not for the data itself, which stays open.

One key, 128 APIs, free to start

500 tokens a month without a card. Most calls cost one token.

Create a free account