Public Holidays by Country and Year - Dates and Local Names avatar

Public Holidays by Country and Year - Dates and Local Names

Pricing

from $0.50 / 1,000 results

Go to Apify Store
Public Holidays by Country and Year - Dates and Local Names

Public Holidays by Country and Year - Dates and Local Names

Every public holiday for a country and year as flat rows - date, local name, English name, scope and type. Free public API, no key.

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

alaudin burki

alaudin burki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 days ago

Last modified

Features

Limited permissions

Share

Public Holidays by Country and Year — Dates and Local Names

Fetch every public holiday the source publishes for one country and one year, as one flat row per holiday: date, English name, local-language name, whether it applies nationally, the regions it covers and its type. The API is public and key-less, and a run is a single request.

How to use

  1. Set Year to a four-digit year and Country code to a two-letter ISO code such as GB, US, PK, AE or DE. If you give neither, the run uses 2026 and GB.
  2. Leave Max rows at its default unless you want a short sample; the whole year usually fits in one response.
  3. Run the Actor. Each holiday becomes one row, sorted by date, and the SUMMARY key-value record reports how many rows came back.

Inputs

InputWhat it doesDefault
yearFour-digit year to fetch holidays for.2026
countryTwo-letter ISO country code, e.g. GB, US, PK, AE, DE.GB
maxItemsStop after this many rows. Capped at 20,000.500
maxPagesAccepted for consistency with other Actors in this family. A holiday response is not paged, so one request is made regardless.5 (no effect)

Example input:

{ "year": 2026, "country": "GB" }

Output dataset

FieldMeaning
dateHoliday date, YYYY-MM-DD. Rows are sorted by this field.
nameHoliday name in English, as the source publishes it.
localNameHoliday name in the country's own language. Often identical to name.
countryCodeTwo-letter ISO 3166-1 code of the country requested.
globaltrue when the holiday applies nationwide; false when it is regional or local.
countiesRegions the holiday applies to, comma-separated ISO 3166-2 codes such as GB-ENG, GB-SCT. Empty when the holiday is national.
typesHoliday type labels, joined into one comma-separated string, e.g. Public, Bank.
launchYearYear the holiday was introduced, when the source records one. Usually null.

Each row also carries id, built from the country, the date and the holiday name (for example holiday:GB:2026-01-01:New Year's Day), plus source, firstSeenAt and scrapedAt. The identifier is stable for a given country, date and name, so consecutive runs line up.

Why this is different

  • One request returns a complete year for a country — there is no pagination loop to tune and no partial result to stitch together.
  • The regional detail is kept rather than flattened away: global tells you whether a date is national, and counties names the regions when it is not.
  • English and local names sit side by side in the same row, so a calendar can be displayed in either language without a second lookup.
  • Dates are sorted before the dataset is written, so the output can be read as a calendar directly.
  • The source needs no key, so a run needs no account setup.

Limitations

  • global: false does not mean the holiday is unimportant — it means it applies to the regions in counties. Read both fields before treating a date as nationwide.
  • The source covers a fixed list of countries, not every country. A code it does not support fails the run with a source error rather than returning an empty dataset.
  • Substitute days and one-off holidays are included by the source and are not marked as such here.
  • Whether a holiday falls on the same date every year is not included; that flag is in the source but not in this output.
  • types and counties are joined into strings because a dataset row must be flat, so they need splitting before use as lists.
  • One year per run. A multi-year calendar means one run per year.
  • Dates are as published at the time of the run; a country can amend or add holidays later.

FAQ

Do I need an API key? No. The endpoint is public and the Actor sends no credentials.

Why is counties empty for some rows? Because global is true for those — the holiday applies to the whole country, so there are no regions to list.

What do the types values mean? They are the source's own labels — Public, Bank, School, Authorities, Optional and Observance — joined with commas. A holiday can carry more than one.

Can I get several years or several countries in one run? Not in one run. The endpoint is per country and year, so run the Actor once for each pair you need.

Why did the run fail for a country code I expected to work? The source publishes a fixed list of countries. A code outside it returns an HTTP error, and the Actor reports it rather than writing an empty dataset that looks like "no holidays".

Pricing and limits

Pricing is per event: one charge per run, and the current price is shown on this Actor's Apify pricing panel. A run makes one request for one country and one year, returns up to 500 rows by default (raisable to 20,000), and does not paginate. Requests time out after 30 seconds and are retried up to three times on rate-limit and server errors. The source itself is free to query.