# Shippo setup for PopMCP

You end up pasting a single Shippo API token into PopMCP, either shippo_live_… for real postage or shippo_test_… for mock labels.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.goshippo.com
- Credentials screen: https://portal.goshippo.com/api-config/api
- Provider docs: https://docs.goshippo.com/docs/guides_general/authentication/

## Before you begin

- A Shippo account. The free pay-as-you-go tier is enough.
- An account role that can see API Configuration. Shippo hides Developer keys from restricted users.
- A funded Shippo account if you want a live key, because a live token buys real postage.
- A free slot. Shippo allows two active live tokens and two active test tokens per account.

## Get your credentials

### 1. Sign in to the Shippo API portal

Open portal.goshippo.com/api-config/api and sign in with your Shippo credentials. The app also answers on apps.goshippo.com.

Screen: https://portal.goshippo.com/api-config/api

### 2. Open API Configuration and Developer keys

In the API Configuration menu select Developer keys. The page splits into Live keys and Test keys.

Screen: https://portal.goshippo.com/api-config/api

### 3. Create the key

Click Create new live key for production, or Create new test key for mock labels.

Screen: https://portal.goshippo.com/api-config/api

### 4. Copy the token before closing the dialog

Copy the full token from the dialog, then click Close.

### 5. Paste the token into PopMCP

Put the value in PopMCP's API Token field and save. Paste the raw token only, starting with `shippo_live_` or `shippo_test_`.

## Fields PopMCP asks for

- API Token (apiToken) [required]: In Shippo go to the dashboard → API → API Keys (Developer Keys) and copy a Live or Test token. A test token (shippo_test_…) buys mock labels with no charge; a live token (shippo_live_…) buys real postage. Sent as an Authorization: ShippoToken header, stored encrypted, used server-side only. The connection is locked to this token's account.

## Verify

PopMCP shows the Shippo connector as Connected and a test call such as listing addresses returns JSON instead of "Authentication credentials were not provided."

## Troubleshooting

### "Authentication credentials were not provided" or 401

Cause: The token was pasted with the ShippoToken prefix attached, or it was truncated on copy.

Fix: Paste only the raw token starting with shippo_live_ or shippo_test_. PopMCP adds the ShippoToken prefix itself.

### Labels come back as mock labels with no tracking

Cause: A test token is connected.

Fix: Create a live key under Developer keys and re-save the connection with the shippo_live_ token.

### The token was never copied before the dialog closed

Cause: Shippo displays the full key only at creation time and masks it afterwards.

Fix: Delete that key from Developer keys and create a new one, copying it before you click Close.

### The create button is greyed out and the page reads "A maximum of two tokens have been created"

Cause: The account already holds two active tokens of that type.

Fix: Delete a key you no longer use from the Key list under Developer keys, then create the new one.

---

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