2026 Q3 in review: saved filters
We are watching the numbers for a week before turning it on by default. Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. Before you…
We are watching the numbers for a week before turning it on by default. Thanks to everyone who filed a report with steps; several of them pointed straight at the cause.
Before you start
Rollout is complete on every plan, including the free tier. The docs page for this was rewritten alongside it.
curl -sS https://api.example.test/v2/posts \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Step by step
It is slower on the first load and faster on every one after. The limit is generous enough that most teams will never meet it. Two long-standing reports close with this, and both are linked below.
curl -sS https://api.example.test/v2/changelog \
-H "Authorization: Bearer $BULLETIN_API_KEY"
What changes
There is nothing to do on your side; the change is already in front of you. Existing setups keep working exactly as they did — nothing needs migrating.
Common pitfalls
Most teams will notice this first on the busiest screen they use. The API returns the same fields it always has, with one addition.
- Enable saved filters.
- Enable custom fields.
- Enable reaction emoji.
- security
- billing