What we learned shipping custom fields
ANAna Andersson1 min read
We will fold the remaining cases in once we have seen this one hold. Anything already in flight when this went out finishes under the old path.
How it works
There is nothing to do on your side; the change is already in front of you. The change is backwards compatible, so integrations built against the old shape carry on unchanged. The API returns the same fields it always has, with one addition.
What changes
The old behaviour is still reachable for a release, behind a setting. It works the same way on the public site and inside the widget, with no configuration to turn on.
Next steps
Large workspaces should see the biggest difference, since the old query grew with the number of items. It is slower on the first load and faster on every one after.
- Enable Zapier triggers.
- Enable granular email preferences.
curl -sS https://api.example.test/v2/posts \
-H "Authorization: Bearer $BULLETIN_API_KEY"
- search
- billing
- enterprise