# Re:amaze setup for PopMCP

You paste three things: your Re:amaze brand address, the email you sign in with, and your API token from Settings, Developer, API Token. The token acts as you, so your Re:amaze role decides what it can do. One connection covers one brand.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://YOUR-BRAND.reamaze.io/api/v1
- Credentials screen: https://reamaze.reamaze.io/kb/advanced-settings/does-re-amaze-have-an-api
- Provider docs: https://www.reamaze.com/api

## Before you begin

- A Re:amaze account you can sign in to. Re:amaze says API access comes with every account.
- To see API Token under Developer in Settings. If it isn't there for you, ask an admin on your account.

## Get your credentials

### 1. Find your brand address

Sign in to Re:amaze and look at the address in your browser: it starts with your brand, as in `acme.reamaze.io`. You can also find it under Brand Settings. If your account has several brands, use the one you want to connect. Each brand needs its own connection, and a custom domain won't work here.

### 2. Open API Token

Open Settings, then under Developer select API Token. Select Generate New Token if you don't have one yet, then copy the token shown. Every user has their own token, and it acts on behalf of that person, so use the account of whoever should appear as the author of replies and notes.

### 3. Paste them into PopMCP

Enter your address in Brand address, the email you sign in with in Login email, and the token in API token. PopMCP checks all three with one small read of your channels. The email and token must belong to the same person. If you generate a new token later, reconnect with the new one.

## Fields PopMCP asks for

- Brand address (brand) [required]: The address you see when you are signed in to Re:amaze, or the brand's address in Brand Settings. Paste it as it is. This is the brand the connection is locked to.
- Login email (email) [required]: The email you sign in to Re:amaze with. It must belong to the same person as the token.
- API token (apiToken) [required]: From Settings > Developer > API Token in Re:amaze. Select Generate New Token if there isn't one yet. Stored encrypted, used server-side only.

## Verify

PopMCP shows Re:amaze as Verified, labelled with your brand's name. Ask for your channels: reamaze_list_channels answers with their names and slugs, or reamaze_get_brand_overview adds staff and status page details.

## Troubleshooting

### "Re:amaze refused this email and API token"

Cause: The email is not the one you sign in with, the token belongs to someone else, or a newer token has been generated.

Fix: Check the email, then copy the current token from Settings, Developer, API Token and connect again.

### "No Re:amaze brand answered at" your address

Cause: The brand address has a typo, or it isn't the one Re:amaze gave the brand.

Fix: Copy the address from your browser while signed in to Re:amaze, or from Brand Settings.

### "That doesn't look like a Re:amaze brand address"

Cause: You entered a custom domain or another site's address. API requests only work on the address ending in .reamaze.io.

Fix: Use the one ending in .reamaze.io, such as acme.reamaze.io.

### A report or satisfaction ratings tool is refused

Cause: The person behind the token doesn't have the access_reports permission.

Fix: Ask an admin to change their role, or reconnect with a token from someone who has it.

### A tool answers that this connection is bound to a brand

Cause: The request asked for another brand. Each connection stays on one brand.

Fix: Connect that brand separately, with its own address.

### A tool answers that Re:amaze is limiting requests

Cause: Re:amaze limits each token to a number of requests a minute, and answers HTTP 429 above it.

Fix: Wait a minute and try again.

---

Source: https://www.docs.popmcp.com/docs/integrations/re-amaze/