Convertr Help Centre Help Center home page
Submit a request
Sign in
  1. Convertr Help Centre
  2. Product
  3. API Support

ACTION REQUIRED: API Authentication Upgrade Follow

Planned rollout: 1 October 2026

 

Unaffected: Dashboard/browser users — you are not affected by this change

Who this affects: Any system that authenticates to Convertr's API using OAuth access tokens. Review and, if needed, update how your integration stores API access tokens (see below) 

 

We’re upgrading the authentication used by the Convertr API as part of ongoing improvements to platform security and to support exciting new product capabilities that we’ll be rolling out over the coming weeks.

For most customers, there will be no change required. However, if you integrate directly with the Convertr API, there is one thing we recommend checking ahead of the rollout.

 

What’s changing?

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 is not changing. Your existing client credentials and authentication flow will continue to work as they do today.

 

What do I need to check?

If your integration stores or caches Convertr access tokens, please make sure the field used to store them can support tokens of at least 2,048 characters.

We also recommend treating access tokens as opaque values rather than relying on their format or length.

If your integration does not store access tokens, no action should be required.

 

Rollout

We’ll be monitoring the rollout closely and can revert individual accounts to the previous authentication method if we identify an issue.

 

FAQs

Do I need to change my API credentials?
No. Your existing client credentials will continue to work.

Do I need to change how I authenticate to the API?
No. You will continue to request and use access tokens in the same way. The only change you may need to account for is the increased token length.

Does this affect users logging into the Convertr platform?
No. This change relates specifically to API authentication and does not affect normal platform login.

What happens if my integration cannot store the longer token?
API requests using a truncated token may fail authentication. We recommend checking your token storage ahead of the rollout to avoid any disruption.

Can we test this before the rollout?
Yes. Please contact your Customer Success Manager or Convertr Support if you’d like to test your integration ahead of the change.

Articles in this section

  • ACTION REQUIRED: API Authentication Upgrade
  • API Reference: Campaign Duplication API
  • Append/Edit Data to Lead Webhook
  • Campaign Duplication API: Automate Campaign Creation From Your Internal Platforms
  • Convertr API Rate Limits
  • GET Leads v4
  • How to Send Leads Via API
  • POST Delivery Validation with Webhooks
  • POST leads to the Convertr Platform - Campaign Webhook
  • POST leads to the Convertr Platform - Campaign Webhook v2
See more
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top
Convertr