Troubleshooting
This page lists common errors and known issues encountered while integrating Claude Enterprise with Zluri, along with steps to resolve them.
Errors ending in -A appear when you connect the integration. Errors ending in -B appear later, when a scheduled sync fails.
CLE-101-A: The API key used to connect this integration was rejected
This error occurs when Claude does not accept the key entered while connecting Claude Enterprise to Zluri. Common causes:
- The key was not copied in full.
- The key has been revoked.
- The key was created in the Claude Console (platform.claude.com) instead of claude.ai.
To resolve:
-
Verify the API key
- The key must start with
sk-ant-api01-. A key starting withsk-ant-admin01-is a Claude Console key and won't work. - Copy the entire key without extra spaces or characters.
- The key must start with
-
Check the key in claude.ai
- Log in to claude.ai as the Primary Owner and open the API settings page: claude.ai/admin-settings/api-access.
- Under Keys, check that the key is still listed.
- If it is missing, select + Create key and create a new key with the read:members and read:analytics scopes.
- Copy and securely store the new key. It is shown only once.
After creating a new key, reconnect the integration in Zluri. For full steps, see the connect guide.
CLE-101-B: The stored API key is no longer accepted
This error occurs when the sync stops because Claude rejected the key stored for this integration, usually because the key was revoked after the connection was made.
To resolve:
- Log in to claude.ai as the Primary Owner and open the API settings page: claude.ai/admin-settings/api-access.
- Under Keys, check whether the existing key is still listed.
- If it is missing, select + Create key and create a new key with the read:members and read:analytics scopes.
- Reconnect the integration in Zluri using the new key.
CLE-102-A: The API key is missing a required scope
This error occurs when connecting Claude Enterprise to Zluri with a key that does not carry both the read:members and read:analytics scopes. A common cause is following Anthropic's Analytics API guide, which creates a key with only read:analytics.
To resolve:
Scopes can't be changed after a key is created, so create a replacement key.
- Log in to claude.ai as the Primary Owner and open the API settings page: claude.ai/admin-settings/api-access.
- Under Keys, select + Create key and enter a name.
- Select both read:members and read:analytics.
- Copy and securely store the new key. It is shown only once.
After creating the replacement key, reconnect the integration in Zluri.
CLE-102-B: The stored API key no longer carries the required scopes
This error occurs when the sync stops because the key stored for this integration no longer carries both the read:members and read:analytics scopes.
To resolve:
- Log in to claude.ai as the Primary Owner and open the API settings page: claude.ai/admin-settings/api-access.
- Under Keys, select + Create key and select both read:members and read:analytics.
- Copy and securely store the new key.
- Reconnect the integration in Zluri using the new key.
If your issue isn't mentioned here, feel free to submit a ticket or contact us directly at [email protected].
Updated about 6 hours ago
