YourCals

Polling frequencies depend on your plan, ranging from real-time dynamic intervals to scheduled background syncs.

YourCals detects the diff/delta in the iCal feed and instantly triggers an HTTP POST webhook payload to your endpoint.

Because most of that traffic buys you nothing: an unchanged feed still costs a full round trip and a parse to learn that nothing happened. YourCals keeps the validator state per feed, so an unchanged calendar stops at a 304 and only real changes reach your API. The crons, the retry queues and the parser go with it.

An endpoint that accepts a POST and verifies our signature. Everything else is ours: registering feeds through the API or the dashboard, polling them, validating the response, diffing it and delivering the change set. The calendar providers never hear from you.

Monthly or annually, per plan, in euros. The annual price is charged once for twelve months and saves 15% on Starter and 16% on Growth. Webhook deliveries are never metered, so a calendar that moves every hour costs the same as one that never moves.

One iCal or webcal URL, wherever it comes from. If several of your users connect the same public calendar, YourCals fetches it once and notifies each of them, so a popular calendar is not polled once per subscriber.

By default YourCals stores only a hash of each feed. Notify-only mode sends the event name and the feed URL, and nothing from inside the events, which keeps the default plan's data scope minimal.

Nothing is sent. A failed, empty or non-calendar response is treated as missing data rather than as an empty calendar, the feed is paused, and we try again on schedule.

Each delivery is signed with HMAC-SHA256 over the timestamp and the raw body, and sent in the X-Hub-Signature-256 header as t=,v1=. Your receiver recomputes the digest and rejects timestamps older than five minutes, which is what closes the replay window.

Yes. Email sign-up works too, with a one-time code sent to your phone or email to verify the account.