Skip to content
  • There are no suggestions because the search field is empty.

Integrations : SaaS : Postman

Adding the Postman Integration and Its Associated Insights

Overview

The Postman connection in Block 64 enables secure, read-only access to workspace and member data from your organization's Postman team. Postman is an API development and collaboration platform used by teams to design, build, test, and document APIs.

This integration collects information about your organization's Postman workspaces, including active members and workspace access, providing visibility into Postman adoption, team membership, and seat utilization across the organization.

Once connected, the data collected from this integration appears in the following Block 64 Insights report:

Reports → SaaS → Usage – Displays Postman team membership, workspace access, and adoption trends across your organization. For Enterprise accounts with a SCIM Token configured, this also includes inactive user detection and last-activity tracking to support license optimization.

The credentials needed for this Integration

To set up this integration, you'll need:

Postman API Key (required) – An API key generated in your Postman account settings by a user with the Admin or Super Admin role on your Postman team. The API key is required for all plan types; Team accounts only need an API Key.

SCIM Token (optional – Enterprise accounts only) – A SCIM Bearer token generated from the Postman Admin Console. If provided, inactive users and last-login data are collected via the Postman SCIM and audit log APIs, enabling inactive user detection and last-activity tracking.

Create a Postman API Key

  1. Sign in to Postman using an account with the Admin or Super Admin role on your team.
  2. Select your avatar and go to Settings → API Keys (Profile → API Keys).
  3. Click Generate API Key.
  4. Enter a recognizable name for the key (for example, Block 64 Integration).
  5. Copy the API key and store it securely — Postman will not display the full key again after you leave this page.
  6. Sign in to the Postman Admin Console as a Super Admin.
  7. Navigate to Team Settings → Authentication → SCIM.
  8. Ensure that SCIM provisioning is enabled for your team.
  9. Generate a new SCIM API key (Bearer token) and copy it.
  10. In the Block 64 Insights portal, navigate to Integrations → Postman.
  11. In the API Key field, paste the API key generated in Postman.
  12. (Optional – Enterprise only) In the SCIM Token field, paste the SCIM Bearer token generated in the Postman Admin Console.
  13. Ensure the Integration Connection toggle is set to Enabled.
  14. Click Connect to finalize the setup.

            Note: A Postman API key inherits the permissions of the user who created it. If the key is generated by a user without the Admin or Super Admin role, Block 64 will not be able to collect team-level member and workspace data.

            Generate a SCIM Token (Enterprise only – optional)

            To enable inactive user detection and last-activity tracking:

                    If your organization is not on a Postman Enterprise plan, skip this step — the integration works with the API Key alone.

                    How to add this Integration

                              Once the integration is connected and synced, Postman workspace and member data will begin appearing in your Insights reports.

                              Tip: The Integration Connection toggle lets you enable or disable data collection at any time without deleting your integration credentials.

                              Security & Privacy

                              All access is read-only. Block 64 cannot modify, delete, or create any data in your Postman environment.

                              Only metadata relating to team members, workspaces, roles, and activity is collected — collections, environments, request bodies, and API definitions are never read or stored.

                              Data is handled in compliance with Block 64's Privacy Policy and Postman's Terms of Service.

                              Access can be reviewed or revoked at any time by deleting the API key (and SCIM token, if configured) in Postman.

                              Why is this Integration failing?

                              If the integration isn't working, it's usually caused by:

                              • Invalid API Key – The API key entered may be incorrect, or it may have been deleted or regenerated in Postman without being updated in Block 64.
                              • Insufficient role – The API key was generated by a user without the Admin or Super Admin role, so team-level member and workspace data cannot be accessed.
                              • Invalid or expired SCIM Token – The SCIM Bearer token may have been regenerated or revoked in the Postman Admin Console.
                              • SCIM not available on your plan – A SCIM Token was entered, but the Postman team is not on an Enterprise plan, or SCIM provisioning is not enabled.
                              • Integration disabled – The Integration Connection toggle is set to Disabled, pausing data collection.

                                        To fix this:

                                        1. Verify the API key belongs to an active Postman user with the Admin or Super Admin role on your team.
                                        2. If the API key was regenerated in Postman, update it in Block 64 immediately and click Connect again.
                                        3. For Enterprise accounts, confirm SCIM provisioning is enabled in the Postman Admin Console (Team Settings → Authentication → SCIM) and regenerate the SCIM Token if needed.
                                        4. Verify that the Integration Connection toggle is set to Enabled in the Block 64 Insights portal.
                                        5. Sign in to Postman.
                                        6. Go to Settings → API Keys and delete the API key created for Block 64.
                                        7. (Enterprise only) In the Postman Admin Console, navigate to Team Settings → Authentication → SCIM and revoke the SCIM API key created for Block 64.

                                                How to remove this Integration

                                                From Block 64:

                                                You can disable this integration temporarily by clicking on the Enable switch in the integration. This pauses data collection without deleting your integration credentials.

                                                Alternatively, you can disconnect the integration entirely by clicking on the Disconnect button.

                                                To permanently remove all collected data, click Delete Data under Delete Integration Data.

                                                ⚠️ This cannot be undone — all collected data for this integration will be permanently removed, and the integration will be disconnected.

                                                From Postman:

                                                1. Sign in to Postman.
                                                2. Go to Settings → API Keys and delete the API key created for Block 64.
                                                3. (Enterprise only) In the Postman Admin Console, navigate to Team Settings → Authentication → SCIM and revoke the SCIM API key created for Block 64.