Postman
Connect Postman to manage workspaces, collections, environments, mock servers, monitors, and specs for your team.
You end up with a single Postman API key beginning with PMAK- that you paste into PopMCP's API key field.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.getpostman.com
- Rate limits
- 300 requests per minute per API key, on top of a monthly Postman API call allowance that varies by plan.
Before you begin
- A Postman account. The Free plan is enough.
- If you belong to a Postman team, an Admin must leave Allow anyone in your team to generate API keys turned on.
- Access to the workspaces you want PopMCP to reach. The key inherits your own Postman permissions.
Get your credentials
Open your Postman account settings
Sign in at go.postman.co and click the gear icon in the top right of the Postman header. Choose Settings, then Account settings.
Open API keys and start a new key
In the account settings sidebar click API keys, then click Generate API Key.
API keys
Use a Postman API key to authenticate requests to the Postman API.
| Name | Key | Last used | Expires | Status |
|---|---|---|---|---|
| Local scriptsCreated Mar 4, 2026 | PMAK-****71bd | Aug 12, 2026 | Never | Active |
| CI runnerCreated Jan 9, 2026 | PMAK-****02e8 | Jul 30, 2026 | Sep 9, 2026 | Revoked |
On a managed team the Generate API Key button is greyed out until an Admin allows member keys.
Name the key and generate it
Type a name you will recognise later, such as PopMCP, set an expiry if you want one, then click Generate API Key.
API keys
Use a Postman API key to authenticate requests to the Postman API.
Copy the key into PopMCP
Click Copy in the dialog, then paste the key into the API key field on PopMCP's Postman connect form.
API keys
Use a Postman API key to authenticate requests to the Postman API.
PopMCP sends the key as the X-API-Key header.
Connect in PopMCP
Open your workspace, choose Postman in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | In Postman open Account settings → API keys (https://go.postman.co/settings/me/api-keys) → Generate API key, give it a name, and copy it (Postman shows it once; it starts with PMAK-). It's sent as the X-API-Key header and stored encrypted; used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Postman immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Postman connector in PopMCP flips to Connected and a tool call such as listing workspaces returns your workspace names instead of an authentication error.
Troubleshooting
401 with "Invalid API Key. Every request requires a valid API Key to be sent."
Why: The key was mistyped, truncated on paste, or has been revoked.
Fix: Generate a fresh key on the API keys page and paste the whole PMAK- string with no leading or trailing spaces.
You closed the dialog before copying the key
Why: Postman shows a new key once. After the dialog closes it can only be revoked or regenerated, never shown again.
Fix: Use the more actions icon next to the key on the API keys page to regenerate or delete it, then create a replacement.
The Generate API Key button is disabled
Why: A team Admin turned off "Allow anyone in your team to generate API keys".
Fix: Ask a Postman Admin or Super Admin to re-enable key generation, or to issue you a key.
The connector worked and then stopped
Why: The key hit its expiry, or Postman's Secret Scanner auto-revoked it after finding it published somewhere public.
Fix: Generate a replacement key, update it in PopMCP, and keep the key out of public repos and collections.
429 Too Many Requests
Why: More than 300 calls in a minute on that key, or the plan's monthly Postman API allowance is used up.
Fix: Slow the calls down and check your plan's Postman API usage in billing.