Re:amaze
Connect Re:amaze to work your shared inbox, reply to customers, manage contacts and help articles, and post status page updates.
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.
- Setup time
- 2 min
- Auth
- API credentials
- API base URL
- https://YOUR-BRAND.reamaze.io/api/v1
- Rate limits
- Re:amaze limits each API token to a number of requests a minute and doesn't publish the number. Over the limit, it answers HTTP 429.
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
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.
Brand Settings
PopMCP accepts acme, acme.reamaze.io or the whole address from your browser.
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.
API Token
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.
Connect in PopMCP
Open your workspace, choose Re:amaze in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Brand addresstext | 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 emailtext | The email you sign in to Re:amaze with. It must belong to the same person as the token. |
| API tokensecret | From Settings > Developer > API Token in Re:amaze. Select Generate New Token if there isn't one yet. Stored encrypted, used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Re:amaze immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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"
Why: 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
Why: 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"
Why: 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
Why: 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
Why: 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
Why: 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.