# Route setup for PopMCP

You paste one Secret API token from the Route dashboard. The token belongs to one merchant account, so there is nothing else to choose.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.route.com
- Credentials screen: https://dashboard.route.com
- Provider docs: https://docs.route.com/docs/protect-v2/5w41yjkjx9z88-authentication

## Before you begin

- A Route merchant account. You can make one at dashboard.route.com/onboarding/account-creation
- A login to the Route dashboard, or the email Route sent you when the account was made, because both have your token

## Get your credentials

### 1. Find your Secret API token

Sign in at dashboard.route.com and open the Admin section. Your tokens are there. Route also emailed them to you when your account was made, so you can copy the token from that email instead.

Screen: https://dashboard.route.com

### 2. Choose the right token

Copy the Secret token to work with your real orders. To try things first, copy the Test-Secret token, which starts with `test-`: Route flags the orders it creates as test orders. Do not use the public API key, because it only works in the storefront widget.

### 3. Paste it into PopMCP

Open the Route connector in PopMCP. Paste the token into Secret API token and click Connect. PopMCP checks it with Route and marks the connection as live or test.

### 4. Add your merchant ID (optional)

To price protection quotes without being asked for it each time, open More options and paste your Merchant ID, which starts with `merch_`. It is shown in the Route dashboard. Everything else works without it.

## Fields PopMCP asks for

- Secret API token (apiToken) [required]: In the Admin section of the Route dashboard. Route also emailed it when your account was made.
- Merchant ID (merchantId): Only used to price protection quotes, so your AI does not have to ask. It starts with merch_ and is shown in the Route dashboard.

## Verify

PopMCP marks Route Connected and shows whether the token is live or test. Asking where a package is, with its tracking number and order number, returns its status.

## Troubleshooting

### Route did not accept this token

Cause: The token was cut off when pasted, or it is the public API key.

Fix: Copy the Secret API token again from the Admin section of the Route dashboard and paste the whole value.

### Route knows this token, but says it may not read shipments

Cause: This can be the public API key, or a merchant account Route has not enabled for this call.

Fix: Paste the Secret API token. If that is what you pasted, ask Route support to enable API access for your account.

### The AI cannot list my orders, or read a claim

Cause: Route publishes no call to list orders or shipments, read an order, or read or file a claim.

Fix: Give the AI the order number and tracking number, and use the Route dashboard for claims.

### A package comes back as not found

Cause: Route needs both the tracking number and the store's own order id, and a shipment exists only after it has been sent to Route.

Fix: Check both values. If the package was never sent to Route, ask the AI to add it to the order.

### A quote says there is no agreement for this merchant

Cause: The merchant ID is wrong, or the account is not set up for Route Protect.

Fix: Check the merchant ID in the Route dashboard. If it is right, ask Route support.

---

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