Wednesday 05 August
Action Required
API Authentication Upgrade
We're upgrading the authentication used by the Convertr API as part of ongoing improvements to platform security and to support new product capabilities we'll be rolling out over the coming weeks.
API access tokens will move to a new format and will be longer than the tokens issued today. The way you request and use access tokens isn't changing — your existing client credentials and authentication flow will continue to work as they do today.
Who's affected: Systems that authenticate to Convertr's API using OAuth access tokens. Dashboard/browser users are not affected.
What to check: If your integration stores or caches Convertr access tokens, make sure the field used to store them can support at least 2,048 characters. We recommend treating access tokens as opaque values rather than relying on their format or length. If your integration doesn't store access tokens, no action is required.
Planned rollout: 1 October 2026
We'll be monitoring the rollout closely and can revert individual accounts to the previous authentication method if we identify an issue. If you'd like to test your integration ahead of the change, contact your Customer Success Manager or Convertr Support.
For full details and FAQs, see ACTION REQUIRED: API Authentication Upgrade.