---
updatedAt: 2025-09-09T21:46:03.000Z
agentTools:
  projectIndex: https://help.zluri.com/llms.txt
---

# Troubleshooting

This page contains a list of common errors and known issues encountered while integrating Postman with Zluri, and instructions on how to fix them.

If your issue isn’t mentioned here, feel free to [submit a ticket](https://support.zluri.com/support/tickets/new) or contact us directly at <support@zluri.com>.

### POST-100-A: *The API key used for this integration is incorrect*

This error occurs while connecting Postman to Zluri with an incorrect API key.

To resolve this error:

* Ensure you are generating the API key correctly in Postman:

  1. Go to **Postman** → **Settings** → **API Keys**
  2. Click **Generate API Key**
  3. Provide a meaningful name for the key
  4. Copy the generated API key immediately
  5. Store it securely as it won't be shown again

* Verify that you are copying the API key correctly:
  * Copy the entire key without any extra spaces or characters
  * Ensure no characters are missing from the beginning or end
  * The key should be pasted exactly as generated
  * Confirm you're using the correct region (US or EU) that matches your Postman account

After generating a new API key, try to connect the integration again.

### POST-100-B: *The API key used for this integration is expired/revoked*

This error occurs when the API key used to connect Postman to Zluri has expired or been revoked.

Common causes include:

* The API key was manually deleted from Postman settings
* The user who created the API key was deactivated
* API key rotation policies caused the key to expire
* Team settings changed to revoke existing keys

To resolve this error:

1. Go to **Postman** → **Settings** → **API Keys**
2. Check if your existing API key is still listed and active
3. If the key is missing or inactive, create a new API key:
   * Click **Generate API Key**
   * Provide a descriptive name
   * Copy the new key immediately
4. Use the new API key to reconnect the integration in Zluri

### POST-101-A: *The user trying to connect the integration does not have sufficient permissions to access users*

This error occurs when the Postman user does not have the necessary privileges to access user information.

To resolve this error, ensure the user has one of the following roles:

* **Team Admin**
* **Team Lead**
* **Billing** (with appropriate permissions)

Additionally, verify that:

* The user can access the Team section in Postman
* The account has the necessary plan that includes user management features
* No custom role restrictions are blocking user data access
* The API key was generated by a user with sufficient permissions

After updating the permissions, try to connect the integration again.

### POST-101-B: *The permissions associated with the users who connected this integration have been modified*

This error occurs when the Postman user who connected to Zluri has lost the required permissions to access users.

To resolve this error:

1. Verify the original user still has appropriate permissions:

   * **Team Admin**
   * **Team Lead**
   * **Billing** (with user access)

2. Check if the user's role was modified or downgraded

3. Ensure the user can still access the Team section in Postman

4. Reconnect the integration with a user having the required permissions to access users

### POST-102-A: *The user trying to connect the integration does not have sufficient permissions to access workspaces*

This error occurs when the Postman user cannot access workspace information.

To resolve this error:

* Ensure the user has appropriate workspace permissions:

  * **Team Admin** or **Team Lead** role
  * **Workspace Admin** for specific workspaces
  * **Editor** role with workspace access permissions

* Verify that:
  * The user can view workspaces in the Postman interface
  * At least one workspace exists in the team
  * The user hasn't been removed from all workspaces
  * Workspace visibility settings allow API access

### POST-102-B: *The permissions associated with the users who connected this integration have been modified*

This error occurs when the user who connected the integration has lost workspace access permissions.

To resolve this error:

1. Restore workspace access permissions for the original user, or
2. Reconnect the integration with a user having the required permissions to access workspaces
3. Ensure the new user can view and manage team workspaces

### POST-103-A: *The user trying to connect the integration does not have sufficient permissions to access roles*

This error occurs when the Postman user cannot access role information within workspaces.

To resolve this error:

* Ensure the user has **Team Admin** or **Team Lead** privileges
* Verify that the user can manage workspace roles and permissions
* Check that role management is available in your Postman plan
* Confirm the user can access workspace settings and member management

### POST-103-B: *The permissions associated with the users who connected this integration have been modified*

This error occurs when the user who connected the integration has lost permissions to access roles.

To resolve this error:

1. Restore role management permissions for the original user
2. Ensure the user has **Team Admin** or **Team Lead** privileges
3. Reconnect the integration with a user having the required permissions to access roles

### POST-104-A: *The user trying to connect the integration does not have sufficient permissions to access audit\_logs*

This error occurs when the Postman user cannot access audit log information.

To resolve this error:

* Ensure the user has **Team Admin** privileges
* Verify that your Postman team is on an **Enterprise** plan
* Check that audit logging is enabled in your team settings
* Confirm the user can access **Team** → **Settings** → **Audit Logs**
* Ensure the API key includes the `Postman.audit_logs.read` scope

### POST-104-B: *The permissions associated with the users who connected this integration have been modified*

This error occurs when the user who connected the integration has lost permissions to access audit logs.

To resolve this error:

1. Restore audit log access permissions for the original user
2. Ensure the user has **Team Admin** privileges
3. Verify the team is still on an Enterprise plan
4. Reconnect the integration with a user having the required permissions to access audit\_logs

### POST-105-A: *Your Postman team is not in the Enterprise plan. Please upgrade to the Enterprise plan to access Audit Logs*

This error occurs when trying to access audit logs without an Enterprise subscription.

To resolve this error:

* Upgrade your Postman team to the **Enterprise** plan:

  1. Go to **Team** → **Settings** → **Plan & Billing**
  2. Click **Upgrade** to Enterprise
  3. Complete the billing setup
  4. Verify audit log access is now available

* Alternatively, if audit logs are not required:
  * Contact Zluri support to configure the integration without audit log access
  * Use a different integration scope that doesn't require Enterprise features

### POST-105-B: *Your Postman team Enterprise plan is ended. Please upgrade to the Enterprise plan to access Audit Logs*

This error occurs when the Enterprise subscription has expired or been downgraded.

To resolve this error:

1. Renew your Enterprise subscription:

   * Go to **Team** → **Settings** → **Plan & Billing**
   * Resubscribe to the Enterprise plan
   * Ensure billing information is current

2. After upgrading, reconnect the integration to restore audit log access

### POST-106-A: *The Postman team does not exist anymore*

This error occurs when the Postman team being connected no longer exists.

To resolve this error:

* Verify you're connecting to the correct Postman team:

  * Check the team URL and name
  * Ensure you haven't been removed from the team
  * Confirm the team wasn't deleted or merged

* If the team no longer exists:
  * Connect to a different, valid Postman team
  * Contact your organization admin to verify team status
  * Ensure you have access to an active Postman team

### POST-106-B: *The Postman team does not exist anymore*

This error occurs during sync when the connected Postman team has been deleted or no longer exists.

To resolve this error:

1. Verify the current status of your Postman team
2. If the team was deleted or merged:
   * Reconnect the integration with a valid, active Postman team
   * Ensure you have appropriate permissions in the new team
   * Update any team-specific configurations as needed

***

If your issue is not listed here, please contact Zluri support with the error details for further assistance.