# Postman setup for PopMCP

You end up with a single Postman API key beginning with PMAK- that you paste into PopMCP's API key field.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.getpostman.com
- Credentials screen: https://go.postman.co/settings/me/api-keys
- Provider docs: https://learning.postman.com/docs/developer/postman-api/authentication/

## 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

### 1. 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.

Screen: https://go.postman.co/settings/me

### 2. Open API keys and start a new key

In the account settings sidebar click API keys, then click Generate API Key.

Screen: https://go.postman.co/settings/me/api-keys

### 3. 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.

### 4. 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.

## Fields PopMCP asks for

- API key (apiKey) [required]: 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.

## Verify

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."

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/postman/