# Public Holidays API — 100+ countries (no key) (`synthetic.ia/public-holidays`) Actor

Official public holidays for 100+ countries: all holidays by year, upcoming holidays, is-today-a-holiday, long weekends, and country info. Data from Nager.Date. Clean HTTP API + MCP, no key. Pay per query.

- **URL**: https://apify.com/synthetic.ia/public-holidays.md
- **Developed by:** [Synthetic](https://apify.com/synthetic.ia) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 holiday queries

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Public Holidays API — 100+ countries (no key)

Official **public holidays** for 100+ countries as a clean HTTP API (and MCP tool). Look up every holiday for a country and year, the **upcoming** ones, whether **today** is a holiday, **long weekends** (with the bridge days to take off), and basic **country info** — all keyless. Perfect for scheduling, payroll, delivery/SLA calculations, booking flows and agents that need to reason about the calendar. **No API key.** Pay per query.

- 📅 **Holidays by year** — every public holiday for a country in a given year (local + English names, date, global/regional).
- ⏭️ **Upcoming** — the next holidays for a country, or worldwide.
- ✅ **Is today a holiday?** — a quick boolean per country.
- 🌉 **Long weekends** — date ranges + which bridge days to take.
- 🌍 **Country info & list** — names, region, land borders, and all supported countries.
- 💵 Pay per query · no key.

### The use case it was built for

Anything date-aware breaks on holidays: SLAs, payroll, "next business day", delivery estimates, booking availability, reminders. Instead of hard-coding calendars per country, ask this API. Give an agent (over MCP) the ability to answer "is the office open tomorrow in Spain?" or "when's the next long weekend in Argentina?".

### Sample output (`holidays`, AR 2026)

```json
{
  "ok": true, "country": "AR", "year": 2026, "count": 19,
  "holidays": [
    { "date": "2026-01-01", "localName": "Año Nuevo", "name": "New Year's Day",
      "countryCode": "AR", "global": true, "types": ["Public"] }
  ]
}
```

### How to use

- **HTTP API (Standby):** POST or GET `/holidays`, `/next`, `/is-today`, `/long-weekends`, `/country-info`, `/countries`. `GET /` returns help. Example: `GET /next?country=AR&limit=3`.
- **Normal run:** pass `{ operation, country, year }`; results land in the dataset + key-value store.
- **MCP tool:** expose it to your agent via Apify's MCP server.

### Input

- **operation** — `holidays` · `next` · `is-today` · `long-weekends` · `country-info` · `countries`.
- **country** — 2-letter ISO code (AR, US, ES, BR…). Optional for `next` (worldwide) and `countries`.
- **year** — for `holidays` / `long-weekends` (default: current year). **limit** — cap `next` results.

### Pricing

**Per query** from **$0.005** (down to $0.002 on higher tiers). One call = one query.

### Related Actors

- **[Open-Meteo Weather API](https://apify.com/synthetic.ia/open-meteo-weather)** — forecasts and history for the same planning use cases.

### FAQ

**Which countries?** 100+ — call `countries` for the full list. Use 2-letter ISO codes.

**Are regional/state holidays included?** Holidays carry a `global` flag and (where relevant) county codes, so you can filter national vs regional.

**Do I need a key?** No.

### Notes & limits

Data comes from Nager.Date (community-maintained, widely used). Always sanity-check against local sources for legally binding decisions.

# Changelog

This Actor's version history is a separate document: https://apify.com/synthetic.ia/public-holidays/changelog.md

# Actor input Schema

## `operation` (type: `string`):

What to fetch.

## `country` (type: `string`):

2-letter ISO country code, e.g. AR, US, ES, BR. Optional for 'next' (worldwide) and 'countries'.

## `year` (type: `integer`):

Year for holidays / long-weekends. Default = current year.

## `limit` (type: `integer`):

Max upcoming holidays to return.

## Actor input object example

```json
{
  "operation": "holidays",
  "country": "AR"
}
```

# Actor output Schema

## `result` (type: `string`):

No description

## `runs` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "country": "AR"
};

// Run the Actor and wait for it to finish
const run = await client.actor("synthetic.ia/public-holidays").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "country": "AR" }

# Run the Actor and wait for it to finish
run = client.actor("synthetic.ia/public-holidays").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "country": "AR"
}' |
apify call synthetic.ia/public-holidays --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,synthetic.ia/public-holidays"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nLJZBoar2NRUcabpF/builds/uNqHejhaLSFkfewNL/openapi.json