This release makes it possible to use an OAuth 2 client credentials workflow to authenticate workflow webhooks in Iterable. This means that Iterable can periodically fetch new access tokens so that they don't expire.
To use OAuth 2 with a workflow webhook, Iterable uses a client ID and client
secret that you provide to fetch an access token from your authorization server.
Then, it authenticates webhook requests by including this token as a header:
Authorization: Bearer <ACCESS_TOKEN>.
Iterable refreshes access tokens at least every 10 days. Additionally, if an expired
access token results in a
401 Unauthorized response, Iterable will fetch a new
access token and try the request again.
To learn more, read Workflow Webhooks.
If you have questions about this update, talk to your customer success manager.