Three questions the public site should answer
The change is backwards compatible, so integrations built against the old shape carry on unchanged. Large workspaces should see the biggest difference, since the old query grew with the number of items.
Before you start
We rewrote this part rather than patching it, because the old approach ran out of room. We are watching the numbers for a week before turning it on by default. It is slower on the first load and faster on every one after.
What changes
Most teams will notice this first on the busiest screen they use. The old behaviour is still reachable for a release, behind a setting. We will fold the remaining cases in once we have seen this one hold.
- Enable SAML SSO.
- Enable an audit log.
- Enable CSV export.
Common pitfalls
If you were using the workaround, you can drop it — the built-in path covers the same ground. It works the same way on the public site and inside the widget, with no configuration to turn on.
curl -sS https://api.example.test/v2/posts \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Next steps
The docs page for this was rewritten alongside it. The API returns the same fields it always has, with one addition.
- Enable custom fields.
- Enable reaction emoji.
- integrations
- enterprise
- accessibility