Calendar · head-to-head
Church Calendar vs Google Calendar
Church Calendar (calapi) serves the daily Roman Catholic liturgical calendar — season, week, feast rank, and liturgical color — for a given date and country-specific calendar variant, in English, Czech, Latin, or Spanish. It's a small keyless JSON API maintained by a Czech developer alongside the printed liturgical calendars he publishes. There's no pricing or account system of any kind; the only quirk is that its real backend still only serves plain HTTP, timing out on HTTPS.
The Google Calendar API reads and writes events, calendars, free/busy data, and reminders for any Google account that's granted OAuth consent, with push-notification channels available so an app can watch a calendar for changes instead of polling it. It's the same REST API that powers Calendar add-ons and third-party scheduling tools like Calendly. Usage is free under Google's shared per-minute and per-project quotas (10,000 requests/minute/project as of the May 2026 quota update); there's no separate paid tier for the API itself, only future overage billing above a 1,000,000-requests-a-day threshold.
| Church Calendar | Google Calendar | |
|---|---|---|
| Authentication | None | OAuth |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | yes | yes |
| HTTPS | No | Yes |
Church Calendar needs no API key, while Google Calendar requires OAuth — pick Church Calendar to start without signup.