Calendar · head-to-head
Google Calendar vs Hebrew Calendar
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.
Hebcal converts between Gregorian and Hebrew dates and computes Shabbat start/end times, holiday dates, Torah readings, and the Daf Yomi study cycle for any location, driven by the same open-source engine (@hebcal/core) that runs the hebcal.com website. Every endpoint is keyless JSON (or RSS/iCal on other routes) under a Creative Commons Attribution 4.0 license, so results can be reused commercially as long as Hebcal is credited. It's rate-limited to keep the free service polite — no more than 90 requests per 10-second window — and the once-http-only backend now serves over HTTPS as well.
| Google Calendar | Hebrew Calendar | |
|---|---|---|
| Authentication | OAuth | None |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
Hebrew Calendar needs no API key, while Google Calendar requires OAuth — pick Hebrew Calendar to start without signup.