# Redo setup for PopMCP

Two values from one Redo page: the 24-character Store ID, and the API secret created by adding an API client, which is shown only once.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.getredo.com/v2.2
- Credentials screen: https://app.getredo.com/
- Provider docs: https://developers.redo.com/docs/api-reference/authentication

## Before you begin

- A Redo merchant account with dashboard access at app.getredo.com
- A role that carries the Manage team development permission, since Settings then Developer is hidden without it
- The dashboard and API still live on getredo.com even though Redo's marketing site is now redo.com

## Get your credentials

### 1. Open Settings then Developer

Sign in at app.getredo.com and click Settings in the left sidebar. Open Developer.

Screen: https://app.getredo.com/

### 2. Copy the Store ID

Copy the 24-character Store ID from the General section at the top of the page. If you cannot see it, copy any dashboard URL containing `/stores/<id>/` and paste that instead.

### 3. Add an API client

Click Add API Client, name it something you will recognise such as `PopMCP`, and tick the scopes you need. Click Create.

Screen: https://app.getredo.com/

### 4. Copy the API secret while it is on screen

Copy the secret from the confirmation dialog and store it somewhere safe. Dismiss the dialog only once you have it.

### 5. Paste both values into PopMCP

Open the Redo connector in PopMCP. Paste the id into Store ID and the secret into API Secret, then click Connect.

## Fields PopMCP asks for

- Store ID (storeId) [required]: Redo dashboard (app.getredo.com) → Settings → Developer. It's a 24-character id. Paste just the id, or a dashboard URL that contains it (…/stores/<id>/…) and we'll pull it out.
- API Secret (apiSecret) [required]: Redo dashboard → Settings → Developer → Add API Client → copy the generated secret (shown only once). Sent as the Authorization: Bearer header. Stored encrypted; used server-side only. The connection is locked to this secret's store.

## Verify

PopMCP marks the Redo connector Connected and echoes the store it resolved. Asking for recent returns lists real return ids from that store rather than an empty array.

## Troubleshooting

### 401 Unauthorized

Cause: The API secret was truncated on paste, or the API client was deleted under Settings then Developer.

Fix: Create a new API client and paste the full secret. The old one cannot be revealed again.

### 404 on every call even though the secret is valid

Cause: The Store ID is wrong. Redo paths are store scoped, so a bad id fails before auth is checked.

Fix: Re-copy the 24-character id from the General section, or paste a dashboard URL containing /stores/<id>/ and let PopMCP pull it out.

### 403 Forbidden on some tools only

Cause: The API client is missing the scope that endpoint needs. The response names the missing scope.

Fix: Edit the client's scopes under Settings then Developer. Redo applies the change without reissuing the token.

### Developer does not appear under Settings

Cause: Your seat lacks the Manage team development permission, or you are on redo.com rather than the dashboard.

Fix: Ask a Redo store admin to create the client, and sign in at app.getredo.com.

---

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