Clickatell supports multiple formats for its messaging APIs – especially since over the last 20 years, new technologies and standards have emerged.
Instead of retiring older APIs (also known as ‘deprecation’), Clickatell continues to support many of the most popular integrations provided by SMS Gateway (formerly known as ‘Developer Central’).
However, the (newer) Clickatell Portal has a different API signature with an improved authentication model, which at face value is incompatible with the original SMS Gateway.
Fortunately, there is a workaround that enables older integrations (especially those undertaken by third-party platform providers) to function with the new Clickatell Portal.
Your current Clickatell account offers an API Key to integrate with third-party applications. Clickatell’s older account type, i.e., SMS Gateway, uses the API ID and other account credentials to integrate.
On your third-party application, first, see if you can find a space for the API Key:
If you find a space for the API Key, please enter the API Key that is found in your Clickatell account (My Workspace -> API Integrations -> Select API -> API Details). Then you can start testing the integration.
If you absolutely cannot find a space to enter an API Key, but you can find a space for an API ID, follow the instructions below.
Older API signatures require the following authorization credentials:
API ID (short number; < 7 characters)
The equivalent fields from the (newer) Clickatell Portal to use are:
The API Key (from the API section)
SMS and two-way channels, automation, call center integration, payments – do it all with Clickatell’s Chat Commerce platform.