Troubleshooting

BUK-100-A: The API Token used to connect this integration is invalid

This error occurs when connecting BUK to Zluri with an invalid or missing API Token.

To resolve:

1. Verify the API Token
   1. Ensure the API Token is copied in full, without any extra spaces or characters at the start or end.
   2. Confirm the token has not been modified since it was generated.
2. Obtain a new API Token
   1. Contact your BUK administrator to generate a new API Token.
   2. Ensure the token has access to the required APIs: Users and Departments.
   3. Copy the token immediately and store it securely.

After obtaining a valid API Token, reconnect the integration in Zluri.

---

BUK-100-B: The API Token used for this integration is expired or revoked

This error occurs when the API Token used to connect BUK to Zluri has expired or been revoked after the initial connection was established.

To resolve:

1. Contact your BUK administrator to verify whether the existing API Token is still active.
2. If the token has expired or been revoked, request a new API Token with access to the Users and Departments APIs.
3. Reconnect the integration in Zluri using the new API Token.

---

BUK-100-C: Invalid Base URL or API configuration

This error occurs when the BUK Base URL entered during connection is incorrect or does not match the expected format.

To resolve:

1. Verify the Base URL format: https://<your-domain>.buk.<region> (for example: https://company.buk.cl).
2. Ensure the correct domain and region are used for your organization's BUK instance.
3. Confirm there are no trailing slashes or extra characters in the URL.
4. Reconnect the integration in Zluri with the correct Base URL.

---

BUK-101-A: Insufficient permissions to access user data

This error occurs when the API Token provided during connection does not have the necessary permissions to access BUK user data.

To resolve:

1. Contact your BUK administrator to verify that the API Token has access to the Users API endpoint.
2. Ensure the token includes permissions for all required APIs: Users and Departments.
3. Reconnect the integration using a token with sufficient permissions.

---

BUK-101-B: Permissions to access user data were revoked after connection

This error occurs when the API Token permissions to access BUK user data were restricted or revoked after the initial connection was established.

To resolve:

1. Contact your BUK administrator to review the current permissions assigned to the API Token.
2. Ensure the token retains access to the Users and Departments API endpoints.
3. If permissions cannot be restored, obtain a new API Token with the required access.
4. Reconnect the integration in Zluri using the updated or new API Token.

---

BUK-102-A: No users found in the BUK account

This error occurs when BUK returns no user data after a successful connection, typically because no active users are present in the configured account or accessible via the API.

To resolve:

1. Log in to your BUK account and verify that active users exist in the system.
2. Confirm that the API Token has access to the correct BUK instance and organization.
3. Verify the Base URL is pointing to the correct BUK environment.
4. If users are present, contact your BUK administrator to confirm the API is returning data correctly.

---

If your issue isn't mentioned here, feel free to submit a ticket or contact us directly at [email protected].