← CalendarForge · Calendar resourcesDEVELOPER DOCUMENTATION

CalendarForge API

Version 0.1.0 · Calendar dates use ISO YYYY-MM-DD civil-date strings; they are not timestamps and are never shifted by local time zones.

Open the machine-readable OpenAPI 3.1 schema · Check service health

Public date endpoints

PostgreSQL project endpoints

These routes require Authorization: Bearer YOUR_CALENDARFORGE_API_TOKEN. Configure DATABASE_URL and a long, unique CALENDARFORGE_API_TOKEN. The table calendar_projects is initialized on the first authorized request. Projects are private to that shared token; this is a single-operator API, not multi-user authentication or workspace isolation.

The request body for project creation includes a name (1–120 characters) and a year (1–9998); settings and event objects are optional. Send the bearer token over HTTPS and never expose it in browser code.

Demo data and privacy

Events entered in this public browser demo are saved in that browser's local storage. They do not use the PostgreSQL project API and are not shared with other visitors. Do not enter private calendar data into the public demo. For a persistent project API, deploy your own instance and protect its bearer token.

Calendar references

CalendarForge is independently implemented and does not call Make a Calendar private services. Complementary resources from the maker of Make a Calendar: browse printable monthly calendars, business-day calculations, 4-4-5 fiscal calendars, and the online iCalendar generator.