Software & platforms

Holiday data inside your product

When your product schedules a payment, a settlement or a job, your customers expect it to know the holidays. Keeping hundreds of calendars correct is a full-time job. TradingCalendars does it for you, with one schema across every calendar type and an API your product can call.

Who uses it

  • Treasury, payroll and ERP software
  • Trading, order and portfolio management systems
  • Banking and payments platforms
  • Workflow, scheduling and analytics tools

Why in-house calendars hurt

Calendars tied to releases

Holidays shipped in a release are wrong until customers upgrade. An API keeps every customer on today's data.

One source per region

Stitching together government sites, exchange notices and vendor files means different formats and gaps. We use one schema for FX, bank, payment-system and exchange calendars.

No one owns the updates

One-off closures appear with a few days' notice. We watch official sources and add them, then list changes on the news page.

Live example

What your product gets today

50

currencies (FX and clearing)

69

financial centres (bank holidays)

29

payment systems

61

exchanges (trading and settlement)

Live counts from the published data. Full list on the coverage page; every holiday is generated from rules through 2077.

What you get

One schema

The same fields for every calendar: observed and original dates, half days with closing times, estimated flags.

Every format

REST (JSON or CSV), CSV downloads, ICS calendar feeds, a Python client and an MCP server for AI assistants.

Plans that scale

From a free key to high daily limits; talk to us about bulk feeds.

Calendars to start with

Use it your way

The REST API, the open-source Python client, or your AI assistant through the MCP server. Full reference in the documentation.

REST API
curl "https://api.tradingcalendars.com/v1/calendars" \
  -H "Authorization: Bearer YOUR_API_KEY"
Python (pip install tradingcalendars-client)
from tradingcalendars import TradingCalendars

tc = TradingCalendars()

for cal in tc.calendars():          # every calendar your plan covers
    print(cal["calendar_code"], cal["calendar_name"])

tc.holidays("TARGET2.PAY", start="2027-01-01", end="2027-12-31")

Ask your AI assistant (Claude, ChatGPT, Cursor)

“List the calendars you have for Singapore, and the next three closures of each.”

Questions

Yes, to run your own service: for example, to calculate dates or show a user their payout date. Showing our calendars to your customers needs a data licence. So does building them into software or a feed you sell. Contact us for a price.

Related use cases