Feeds and scoped subscriptions on every kind of space

2026.10.14-api-feeds

October 14, 2026

The Forumulate team

1 min read

apifeedssubscriptions

Added

One feed writer, more feeds. RSS, Atom and JSON Feed now come from one writer, so the three formats always agree.

Space	Feeds	Narrow with
Changelog	`…/changelog/atom.xml` (beside `rss.xml`)	`?tag=`, `?type=`
Status	`…/status/atom.xml`, `…/status/feed.json`, `…/status/maintenance.ics`	`?component=`, `?severity=`
Events	`…/events/rss.xml`, `atom.xml`, `feed.json`	`?tag=`
Careers	`…/careers/rss.xml`, `atom.xml`, `feed.json` (new roles, dated from first publish)	`?tag=<team>`
Legal	`/public/orgs/{orgId}/legal/rss.xml`, `atom.xml`, `feed.json` (new editions)	`?kind=`

Scoped subscriptions. A subscribe body takes an optional scope to narrow what the subscriber is emailed about: tags, components, kinds, sections or incidents. With no scope, the subscription covers the whole space, as before. If a confirmed subscriber subscribes again, the scope can only widen.

New subscribe doors:

POST /public/…/careers/subscribe: job alerts. Scope tags are teams, and each subscriber gets one email per role, when the role is first published.
POST /public/…/legal/subscribe: new editions. scope.kinds limits it to named documents.
POST /public/…/roadmap/subscribe: status moves and ships. A signed-in reader can also follow one item (PUT …/roadmap/t/{slug}/follow) or a whole board (GET/PUT …/roadmap/follow).
POST /public/…/faq/follow: follow FAQ sections, and get an email when a question in them is added or materially changed. A signed-in reader with a verified email is confirmed at once. Anyone else confirms through double opt-in.
POST /public/…/events/subscribe: event announcements.

Blog, changelog and status subscribe now take scope as well. For example, a status subscriber can follow a single component.

Watching a changelog. GET/PUT/DELETE /public/…/changelog/watch lets a signed-in reader get new releases by notification, email or web push, according to their preferences.