Idempotent API requests
Knock now supports idempotency so that requests can be retried safely without unintended side effects. This release of idempotency is limited to our workflow trigger endpoint. You can know set an idempotency key on your workflow triggers to ensure that Knock doesn't sent duplicate notifications when you retry requests. You can learn more about API idempotency in Knock in our API reference.
We're powering idempotency in Knock with our new open-source Elixir library for powering idempotency on any API. We're calling it One and Done. 😎 You can learn more about how our One and Done library in our announcement blog post.
Notification localization (i18n) support
In case you missed it last week, we just launched Knock Translations, our solution for teams that need to localize their notifications for a global audience. You can learn more in our announcement post.
Angular in-app feed component
One of our customers wrote a great Angular example of our React in-app feed component. You can find it here. If you're a team that uses Angular and wants to ship an in-app feed in a few minutes, this is a great way to do so. Shoutout to Knock customer and community member Chris Graves for this one!
Fixes and improvements
- 🐛 We fixed a bug in our conditions builder where conditions with empty values could not be created.
- 🐛 We fixed a bug in our fetch step where successful requests that resulted in an empty response would show an error status in the Knock dashboard.
- 🐛 We fixed a bug where our rate limits were too specifically scoped.