Issues with importing Postman collection for testing

News Knowledge Base
,
1

How to import specific Postman collections for API testing without loading the entire workspace in the service editor?

Issue Description

When attempting to import a Postman collection for API testing into Studio using an API key, Studio crashes approximately 30 minutes after import. The issue arises due to having over 50 workspaces, each containing 30 or more collections and numerous requests in the Postman account, leading to excessive content being processed by Studio.

Resolution

  1. Copy the API Key:

Navigate to Profile Settings in your Postman account and copy the API key as highlighted in the screenshot (refer to your documentation or user settings in Postman).

960×540 60.6 KB

  1. Paste the API Key in the Service Editor:
    • Open the Service Editor Window in Studio.
    • Locate the File/Link Field and paste the copied API key here.

kb-0EMPa00000Vzx9P.png486×263 23.6 KB

  1. View Collections:

After pasting the API key, Studio should list all the collections from the workspace configured in the Postman account associated with the API key.

  1. Minimize Account Content:
    • To avoid Studio crashes, create a Postman account that contains only the specific workspace, collections, and requests you need.
    • This approach reduces the amount of content being loaded, preventing resource overload.

Alternative Considerations

  • Create a streamlined Postman account with fewer workspaces and collections focused on the testing requirements.
  • Export individual collections manually and import them to Studio instead of using the API key to load all collections.
  • Use Postman’s export option to save only the required collections as JSON files and upload them to Studio directly.

Key Benefits of the Resolution

  1. Prevents Studio crashes by reducing the amount of excessive data being processed.
  2. Streamlines the workspace-focused imports for efficient API testing setup.
  3. Enables selective import of necessary collections, avoiding unnecessary overhead.

This structured solution should help address the issue effectively and allow for smoother integration between Postman collections and the API testing Studio.