Calendar Subscription Feeds
DayTidy Free publishes signed ICS feeds for all bookings, one offering, or one resource. Subscribe from a compatible calendar client to review reservation times alongside your other calendar entries. A subscription is a periodically refreshed feed, not a two-way connection.
Choose the correct scope
Section titled “Choose the correct scope”| Scope | Where to look | Intended use |
|---|---|---|
| All bookings | Booking module settings | Site-wide operational scheduling |
| One offering | That offering’s editor | Follow bookings for one offering |
| One resource | That resource’s editor | Follow bookings assigned to a person, room, or item |
The controls require the corresponding management permissions. Share the smallest scope that meets the recipient’s need.
Subscribe and check
Section titled “Subscribe and check”- Open the relevant feed controls with an authorized account.
- Copy the subscription URL privately.
- In your calendar client, choose its subscribe-by-URL option and paste the feed URL. Use a subscription rather than a one-time file import when you want later updates.
- Open a known booking in DayTidy and compare its session time with the subscribed event.
- Check the calendar client’s timezone and refresh settings if the event appears at an unexpected time or an update is delayed.
DayTidy emits times in UTC; the client displays them in its configured timezone. Apple Calendar, Google Calendar, and Outlook have their own subscription controls and refresh behavior. The interval is controlled by the client, so a saved reservation change need not appear immediately.
Protect and rotate URLs
Section titled “Protect and rotate URLs”A feed URL is a bearer secret: anyone with it can read the scheduling context in that scope. Feeds exclude customer email addresses, phone numbers, payment details, and arbitrary form fields, but can include booking references, offering titles, option/resource context, and status. Do not publish subscription URLs on a public page or include them in screenshots or support posts.
If a URL is shared incorrectly, regenerate it in the relevant controls and replace the subscription in every intended client. The previous URL becomes invalid; rotating it without updating subscribers interrupts their access.
Feed coverage and status
Section titled “Feed coverage and status”The default feed covers sessions from one year in the past through ten years in the future. It reads at most 1,000 booking-line records before grouping them into calendar events, prioritizing ongoing/future sessions and then recent past sessions. A busy feed can omit records within that date range. Use the appropriate offering/resource scope to narrow the feed, and use booking CSV exports for historical reconciliation.
Confirmed and Completed reservations appear as confirmed calendar events; Pending appears tentative. Cancelled, Declined, Failed, and Expired reservations appear with cancelled calendar status. A cancelled event can remain in the subscription, so its presence does not mean the reservation still occupies capacity. Calendar clients may display or hide cancelled events differently.
Limits and troubleshooting
Section titled “Limits and troubleshooting”Subscriptions do not connect a Google/Outlook account, import external busy periods, or block booking availability from an external calendar. They do not provide customer self-rescheduling. If you need to investigate a booking conflict, use DayTidy’s resource and availability rules, not the calendar client’s display alone.
For a stale feed, check the chosen scope, whether its URL was regenerated, and the client’s refresh behavior. Do not regenerate a valid URL as the first response to every delay.