# Squarespace setup for PopMCP

You end up with one Squarespace Developer API Key, generated under Settings → Advanced → Developer API Keys, pasted into PopMCP's API Key field.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.squarespace.com/1.0/commerce
- Credentials screen: https://account.squarespace.com/websites
- Provider docs: https://developers.squarespace.com/commerce-apis/authentication-and-permissions

## Approval required before this works

Squarespace only exposes the Developer API Keys screen on qualifying paid site plans, so Squarespace's own billing tier, not a review, gates whether a working Commerce API key can exist at all.

- Typical wait: Immediate once the site is on a qualifying plan. The key is generated self-serve in seconds; there is no review queue.
- Cost: The site plan itself; keys cost nothing extra. Squarespace lists the Orders, Inventory and Transactions APIs on the Core, Plus, Advanced and legacy Commerce Advanced plans. The Forms API additionally covers Business and Commerce Basic. Sites on lower plans cannot generate keys at all.
- Blocked until approved: Without a qualifying plan there is no Developer API Keys option, so no Orders, Inventory, Products or Transactions calls are possible. On a plan that qualifies for only some APIs, you can generate a key but cannot tick permissions for the APIs your plan excludes, and calls to those endpoints fail on permissions.
- Works meanwhile: Nothing on the commerce endpoints. You can read the API reference and build against the documented schemas, and on a Forms-eligible plan (Business or Commerce Basic) the Forms API works while the commerce endpoints do not.

## Before you begin

- A site on the Commerce Advanced plan, which the Commerce APIs require for Orders, Inventory and Transactions permissions
- Owner or Administrator permissions on the site, since keys are generated inside the site rather than the account dashboard
- Commerce enabled on the site if you want Orders, Products, Inventory or Transactions access

## Get your credentials

### 1. Open the site you want to connect

Sign in at account.squarespace.com and click into the site whose store data PopMCP should read.

Screen: https://account.squarespace.com/websites

### 2. Go to Settings, Advanced, Developer API Keys

In the site's left panel click Settings, scroll down to Advanced, then click Developer API Keys.

### 3. Name the key and set the permissions

Click GENERATE KEY, type `PopMCP` under KEY NAME, then set a level for each API under PERMISSIONS. Choose Read and Write for Orders, Products and Inventory if the agent should act, or Read Only for a reporting connection.

### 4. Copy the key before closing the window

Copy the key from the confirmation window. Squarespace will not show it again.

### 5. Paste the key into PopMCP

Open the Squarespace connector in PopMCP, paste the value into API Key, and save.

## Fields PopMCP asks for

- API Key (apiKey) [required]: Settings → Advanced → Developer API Keys → Generate Key. Give it the permissions you need (e.g. Orders, Products, Inventory). Copy it exactly. It's shown once. It's sent as a Bearer token and stored encrypted; used server-side only. Requires a paid Squarespace plan.

## Verify

PopMCP shows the Squarespace connector as Connected, and a test order listing returns your recent orders rather than a 401.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The key was copied incompletely, was revoked in Squarespace, or belongs to a different site. Keys are scoped to one site.

Fix: Generate a fresh key on the correct site under Settings → Advanced → Developer API Keys and re-paste it.

### 403 Forbidden on one tool only

Cause: That API was left unticked, or was granted Read Only when the tool needs write.

Fix: Keys cannot be re-scoped. Delete the key, generate a new one with the right permission levels, and update PopMCP.

### Orders or Inventory permissions are not offered

Cause: The site is not on the Commerce Advanced plan, or commerce has never been enabled.

Fix: Upgrade the site to Commerce Advanced, then re-open Settings → Advanced → Developer API Keys.

### 429 Too Many Requests

Cause: More than 300 calls in a minute, or more than 100 Create Order calls in an hour on one key.

Fix: Wait out the one-minute cooldown and pace the agent. Bulk order creation needs OAuth rather than an API key.

### Requests are rejected before any permission check

Cause: Squarespace rejects Commerce API requests that arrive without a User-Agent header, and requests sent over plain HTTP.

Fix: Nothing to change in the console. If you are testing with curl, add a User-Agent header and use HTTPS.

---

Source: https://www.docs.popmcp.com/docs/integrations/squarespace/