Redo
Connect Redo to manage returns, exchanges, warranties, refunds, orders, and package protection for your store.
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.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.getredo.com/v2.2
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
Open Settings then Developer
Sign in at app.getredo.com and click Settings in the left sidebar. Open Developer.
Developer
API clients and webhooks for this store.
- Store ID
- 6a2f91c4****4ac4e9
- API base URL
- https://api.getredo.com/v2.2
| Name | Secret | Scopes | Created | Status |
|---|---|---|---|---|
| Storefront syncAPI client | ****4a2f | returns_read, orders_read | Mar 4, 2026 | Active |
Store ID sits in General. API clients are listed underneath it.
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.
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.
Developer
Scopes can be changed later without reissuing the token.
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.
Developer
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.
Connect in PopMCP
Open your workspace, choose Redo in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Store IDtext | 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 Secretsecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Redo immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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
Why: 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
Why: 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
Why: 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
Why: 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.