# Acuity Scheduling setup for PopMCP

You paste two values from one Acuity screen: the numeric User ID and the matching API Key. PopMCP sends them together as HTTP Basic auth.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://acuityscheduling.com/api/v1
- Credentials screen: https://secure.acuityscheduling.com/app.php?action=settings&key=api
- Provider docs: https://developers.acuityscheduling.com/reference/quick-start

## Approval required before this works

No one reviews you, but Acuity (Squarespace Scheduling) only exposes API credentials on the Premium plan - "Custom API and CSS for Developers" is listed as a Premium-tier feature on the Acuity pricing page.

- Typical wait: None - credentials appear immediately once the account is on Premium
- Cost: Per acuityscheduling.com/pricing: Premium is $49/month billed annually or $61/month billed monthly. Starter ($16 annual / $20 monthly) and Standard ($27 annual / $34 monthly) do not include the API.
- Blocked until approved: Everything. On Starter or Standard the API credentials screen does not issue a User ID and API Key, so every request fails 401, and webhooks are unavailable too.
- Works meanwhile: The 7-day free trial runs on the top tier, so you can pull real credentials and build the whole integration before paying; you can also read the docs and model the endpoints.

## Before you begin

- An Acuity Scheduling (formerly Squarespace Scheduling) account on any paid plan
- Owner or admin sign-in. Team-member logins without Business Settings access cannot open Integrations
- The credentials belong to the whole account, so the connection is locked to that one Acuity business

## Get your credentials

### 1. Open Integrations under Business Settings

Sign in at secure.acuityscheduling.com. In the left sidebar scroll to the Business Settings group and click Integrations.

Screen: https://secure.acuityscheduling.com/app.php?action=settings&key=api

### 2. Open Analytics + Custom Integrations and click view credentials

Click Analytics + Custom Integrations in the category menu, then scroll to the API block. Click view credentials, next to the Developer's Site button.

Screen: https://secure.acuityscheduling.com/app.php?action=settings&key=api

### 3. Copy the User ID and API Key

Copy the numeric User ID and the API Key from the expanded panel. The User ID is the Basic-auth username and the API Key is the password.

Screen: https://secure.acuityscheduling.com/app.php?action=settings&key=api

### 4. Paste both values into PopMCP

Put the numeric value in User ID and the secret in API Key, then click connect.

## Fields PopMCP asks for

- User ID (userId) [required]: In Acuity go to Bizz Settings → Integrations → API and click "view credentials". Copy the numeric User ID. This is the account the MCP is locked to.
- API Key (apiKey) [required]: Same screen (Integrations → API → view credentials): copy the API Key. It's sent as HTTP Basic auth and stored encrypted; used server-side only.

## Verify

PopMCP marks Acuity Scheduling as Connected and the appointment-type tool returns your real appointment types instead of an auth error.

## Troubleshooting

### 401 Unauthorized

Cause: The User ID and API Key are swapped, mistyped, or copied with surrounding whitespace. A stray leading space in the key is the most common cause.

Fix: Reopen Integrations, Analytics + Custom Integrations, API, view credentials, and re-copy both values. Make sure the numeric one goes in User ID.

### No API block on the Integrations page

Cause: You are signed in as a team member whose permissions exclude Business Settings, or on a sub-account rather than the owning account.

Fix: Sign in as the account owner or ask them to read the credentials for you.

### The key stopped working after months of use

Cause: Acuity does not email or rotate these on a schedule, so the same pair stays valid until somebody regenerates it.

Fix: Check whether a colleague clicked Regenerate API Key, then re-copy the current pair into PopMCP.

### 429 Too Many Requests

Cause: Acuity limits callers to 10 requests per second and 20 concurrent connections per IP.

Fix: Space out bulk operations. The limit resets immediately, so a short retry with backoff clears it.

---

Source: https://www.docs.popmcp.com/docs/integrations/acuity-scheduling/