A calendar app (Google Calendar, Outlook, Apple Calendar and others) reads the subscription address. It
serves RFC 5545 iCalendar with the shifts from 30 days back to 90 days ahead, overrides and swaps included.
A feed covers either every shift of one schedule, or the subscriber’s own shifts across schedules.
Make a subscription address
Request body
The address is given only here, once; only the token’s SHA-256 is stored. url is built from the
instance’s external address and is null when none is set, in which case put path after the address
MoleSignal is reached at. Each feed in the list has id, schedule_id, schedule_name, created_at and
last_used_at, when a calendar last read it, but no address.
How the calendar app reads it
Every read checks the subscriber again: the account is still active, still in the organization and still
holds schedules.read, and for a schedule feed can still see that schedule. A failed check, a wrong token
or a stopped feed all return 404. Shift titles and descriptions are in the subscriber’s interface
language.
Anyone with the address can see these shifts; reset or stop the feed when it leaks. Last modified on October 31, 2026
