Utilities / API GUIDE

Nager.Date.

Public holiday dates and local names for country-specific calendars.

Documentation reviewed · 16 Sep 2026
Official resource ↗
AUTHENTICATIONNo key
ACCESS / PRICINGFree access
EXAMPLE REQUESTIncluded below
REVIEW STATUSDocs reviewed
THE OVERVIEW

A building block for your next idea.

Add Bulgarian public holidays to a travel planner or team calendar.

Know before you build

The public REST API and offline packages have different access conditions. Offline Docker and NuGet options require a license key. Verify regional coverage and observed-day rules before using dates in business scheduling.

Check current provider documentation ↗

Your first request

Start with this documented example. Replace credential placeholders with your own test credentials. Browser execution depends on the provider’s CORS policy.

cURL REQUEST EXAMPLE
curl --request GET 'https://nagerholidays.com/api/v3/publicholidays/2026/BG'

Practical questions

What can I build with Nager.Date?+

Add Bulgarian public holidays to a travel planner or team calendar.

Does Nager.Date need authentication?+

The reviewed example is listed as “No key”. The public REST API and offline packages have different access conditions. Offline Docker and NuGet options require a license key. Verify regional coverage and observed-day rules before using dates in business scheduling.

Can I call Nager.Date from a browser?+

Browser access depends on the provider’s CORS policy for your origin, method, and headers. The playground makes a direct request and cannot bypass those restrictions.

Sources & confidence

Provider documentation was reviewed on 16 September 2026. This is not a live availability test or an endorsement.

Source catalogs can become outdated. Read our review and attribution policy. Plain-text guide ↗

THE REQUEST WORKBENCH

Meet the data.

Runs in your browser

Edit a request and see what comes back. Your credentials stay in page memory and go directly to the selected API provider.

01 / REQUEST
Provider docs ↗

Choose an HTTPS endpoint.

Query parameters

Authentication

Custom headers +

The browser manages Cookie, Origin, User-Agent, and other restricted headers.

CORS support is required. No proxy. No saved credentials. 30-second timeout · 2 MB response limit.

02 / RESPONSE
Ready when you are
{ }

A little curiosity.
A real response.

Send a request to explore the response.
Nothing runs automatically.

Response bodies are displayed as data. Remote HTML and scripts are never executed.

Take the request with you cURL / JavaScript

Authentication, query values, custom header values, and body content are hidden by default. Check any URL path before sharing.