I just want to add my support for this feature as well. I have already voted on this topic.
Bringing back a full-site or per-user ICS export would be extremely valuable for our community’s workflow. Is there any update on reconsidering what was removed in PR #231?
If there are privacy or implementation concerns, perhaps a private, per-user ICS feed could be considered as a solution.
I’ve added back the capability for ics export via GET /discourse-post-event/events.ics (as of DEV: add ical format response for discourse-post-events index route by tyb-talks · Pull Request #35143 · discourse/discourse · GitHub ) . Do note that this endpoint has a hard limit of 200 events. If your site has more events than that and you want to do a full export, you may iterate through by using the before and after query parameters which accept date strings. We’ll be adding the full list of acceptable parameters for this endpoint to the API docs in due course.
Thanks for merging PR #35143 — great to see the .ics export officially back.
One thing I wanted to check: is there any possibility (or future plan) to authenticate this feed with a user token or API key, similar to how Discourse handles private RSS/Atom feeds (/topics/feed.rss?token=…)?
Right now /discourse-post-event/events.ics seems to work only for public events, which means Outlook / Google Calendar can’t subscribe to private categories.
Even a lightweight token-based approach (per-user or per-site, read-only) would make it possible to securely expose private events in calendar clients without having to proxy the feed through an external script.
Is that something that could be added, or is it already possible through an existing parameter I might have missed?