Setmore
Connect Setmore to book and manage appointments, services, staff, customers, and available time slots.
You end up pasting a single long-lived Setmore refresh token, issued to your account by Setmore's API team, into PopMCP.
Partner application before this connector works
Setmore has no self-service API console. You must hold a Setmore Pro account and email api@setmore.com with your use case; Setmore's team reviews the request and responds with next steps before any credentials exist.
- Typical wait
- Not published. Setmore states only that 'Our team will review your request and respond with next steps.' No turnaround is given anywhere on the developer or support pages, so treat it as unknown and email early.
- Cost
- Setmore Pro is required. setmore.com/pricing lists Pro at $12 per user/month billed monthly or $5 per user/month billed annually; the Free plan does not qualify. The API itself carries no separate fee.
- Blocked until approved
- Everything. Until the team grants access you have no OAuth client and no refresh token, so no appointment, staff, service or customer endpoint can be called.
- Works meanwhile
- Read the API reference at setmore.docs.apiary.io and developers.setmore.com and model your integration against it. Set up a throwaway Setmore account for later testing, since the API operates against live production data.
Where to apply: Email api@setmore.com from the address registered to your Pro account, including your full name, that registered email, and a short description of your planned API use case. There is no web form.
- Requesting from a Free-plan account is the most common failure: Setmore says 'you'll need a Setmore Pro account' before you email, so the upgrade must already be in place.
- The email address you write from must match the account's registered email, or the request cannot be matched to an account.
- Setmore asks for a description of how you'll use the API. A vague 'building an integration' invites a round-trip while they ask what you will actually read or write.
- There is no sandbox. All calls hit live accounts, so testing against your real business calendar can create or cancel genuine appointments.
- Because access is granted by a human over email rather than by a console, there is no status page to check and no way to self-serve a replacement credential later.
- Setup time
- 5 min, plus 1-2 business days for Setmore to reply
- Auth
- API credentials
- API base URL
- https://developer.setmore.com/api/v1
- Rate limits
- Setmore says the developer documentation covers rate limits but publishes no figures publicly.
Before you begin
- A Setmore Pro subscription. The API is not available on the Free plan.
- Access to the mailbox of the email address the Setmore account is registered under
- Patience for Setmore's API team to reply. There is no self-serve key screen.
Get your credentials
Confirm the account is on Setmore Pro
Sign in at go.setmore.com and open Settings → Billing. Confirm the current plan reads Setmore Pro or higher.
Billing
Your subscription, invoices and payment method.
- Registered email
- owner@brightstudio.com
- Account owner
- Dana Reyes
- Time zone
- Australia/Sydney
Setmore has no in-app API key screen. Billing only confirms the plan, and the registered email is the address Setmore will accept an API request from.
Note the registered login email
Open Settings → Your profile and copy the email address shown there. Setmore answers API requests only when they come from that address.
Request API access
Open setmore.com/developers and click Request API access. Email api@setmore.com from the registered address with your name, that email address, and a short description of how you will use the API.
Setmore API
Build with the Setmore API. You'll need a Pro account.
- Credential
- Refresh token
- Plan required
- Setmore Pro
- Typical reply time
- 1-2 business days
There is no button anywhere in the Setmore app that mints a token.
Copy the refresh token out of Setmore's reply
Open the reply from Setmore and copy the refresh token it contains. Take the whole string with no surrounding spaces or line breaks.
Paste the refresh token into PopMCP
Paste the value into the Refresh token field in the PopMCP connect form and save.
Connect in PopMCP
Open your workspace, choose Setmore in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Connection typepreset | A single long-lived token. We exchange it for short-lived access tokens automatically; the refresh token does not expire unless you regenerate it. |
| Refresh tokensecret | The refresh token Setmore issued for your account. Don't have one? On a Setmore Pro plan, email api@setmore.com from your registered address to request API access. Stored encrypted; used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Setmore immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the Setmore connector as Connected and a test call such as listing services returns your real service list instead of an unauthorized_request error.
Troubleshooting
invalid_refresh_token or "no token found for this refresh token"
Why: The token was mistyped, truncated on copy, or Setmore regenerated it for the account.
Fix: Re-copy the whole string from Setmore's email with no surrounding spaces or line breaks. If it still fails, reply to api@setmore.com and ask for the current token.
401 unauthorized_request on every call
Why: The access token minted from the refresh token expired and was not renewed, or the token belongs to a different Setmore account than the data you are querying.
Fix: Reconnect the connector in PopMCP so it mints a fresh access token, then confirm the token was issued for the account that owns the calendar.
Setmore replies that API access is unavailable
Why: The account is on the Free plan, or the request came from an address that is not the registered account email.
Fix: Upgrade to Pro and resend the request from the registered login email shown on Settings → Your profile.
You want to invalidate the token later
Why: The token stays valid indefinitely unless Setmore regenerates it.
Fix: Email api@setmore.com and ask for the token to be regenerated, then re-save the new value in PopMCP.