We have expanded our existing 3CX integration with a new option: the 3CX [Server API] connector. This follows recent changes to 3CX that could cause issues with the existing API integration for some customers when multiple users shared the same API credentials.
Until now, our API integration with 3CX used a user-level connection. Following recent 3CX updates, we discovered that registering a new client with the same Client ID and Client Secret could invalidate an existing client registration. As a result, the Bubble integration could unexpectedly stop working for other users. Because this behaviour is better suited to a server-level implementation, we decided to introduce a separate 3CX Server API connector. This provides an integration option that better supports environments where the connection is configured centrally at server level.
To make the distinction clearer, we have renamed our existing 3CX [API] connector to 3CX [Client API]. In addition, the new 3CX [Server API] connector is now available. Both connectors remain available, allowing partners to choose the integration method that best suits their 3CX environment.
To prevent issues caused by shared API credentials, we now display a warning in the Webconfigurator when configuring the 3CX [Client API] connector. This warning explains that the Client ID and Client Secret must be unique for each user. When multiple users share the same credentials, requesting a new token may invalidate another user's existing client registration.
For situations where API credentials need to be shared, we therefore recommend using the new 3CX [Server API] connector. With this addition, we make the distinction between the two integration methods clearer and help partners configure their 3CX integrations correctly.