If you notice that your API access token suddenly stops working even though it still appears in your Project Settings, it may be because the token is linked to a teammate who was removed from your Customerly project.
When a teammate who created an API token is removed or loses admin permissions, any tokens they created will be deactivated. This can cause errors such as:
{ "error" : { "code" : 0, "message" : "Access token not found." } }This behavior is intended for security reasons, but it can be confusing since the token still shows up in the Public API section without any indication that it is tied to a specific user.
To avoid unexpected interruptions, consider the following best practices:
Before removing a teammate, check if they have created any API tokens that your integrations rely on.
Regenerate and update your integrations with new tokens created by active teammates or admin users.
Keep track of which user created each token to manage access effectively.
Currently, Customerly does not provide a warning when removing teammates about tokens that will be deactivated.