Squarespace
Connect Squarespace to manage orders, products and variants, inventory, transactions, and profiles for your site.
You end up with one Squarespace Developer API Key, generated under Settings → Advanced → Developer API Keys, pasted into PopMCP's API Key field.
Paid plan required before this connector 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.
Where to apply: There is no application. Upgrade the site's plan in Squarespace billing, then open the Developer tools panel, choose Developer API Keys, click Generate Key, name it and tick the specific API permissions and read or read-write level. The key value is shown only once.
- Plan names changed: newer sites are on Core/Plus/Advanced while older sites sit on legacy Business/Commerce Basic/Commerce Advanced. Guides written for the old names mislead about which tier unlocks which API.
- The key value is displayed only at creation and cannot be retrieved afterwards; lose it and you generate a new one.
- Permissions are chosen at creation. To change what a key can reach you generate a replacement, which means swapping the credential in any live integration.
- Each key is scoped to a single site, so a multi-site account needs one key per site.
- Because access is tied to the plan, downgrading the site removes the API entitlement and existing keys stop working.
- OAuth is a separate path from API keys and is not instant: you must register as an OAuth client through Squarespace's developer apps portal, supplying an app name, icon, redirect URIs and links to your Terms of Service and Privacy Policy, and Squarespace reviews the registration before returning a client ID and secret. Some features, such as the Initiate URL, apply only to Squarespace partner apps.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.squarespace.com/1.0/commerce
- Rate limits
- 300 requests per minute per key, about five per second, returning 429 with a one-minute cooldown. Create Order is further limited to 100 requests per hour per site when using an API key.
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
Open the site you want to connect
Sign in at account.squarespace.com and click into the site whose store data PopMCP should read.
Go to Settings, Advanced, Developer API Keys
In the site's left panel click Settings, scroll down to Advanced, then click Developer API Keys.
Developer API Keys
Create keys for custom applications built on the Squarespace Commerce APIs.
| Key name | Permissions | Created |
|---|---|---|
| Warehouse syncCreated by ops@example.com | Orders (Read), Inventory (Read and Write) | Mar 4, 2026 |
Listed keys show the name and permissions only. A trash icon beside each row revokes it.
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.
Generate Key
Permissions cannot be changed after the key is created.
Webhook Subscriptions is OAuth only and cannot be granted to a Developer API key.
Copy the key before closing the window
Copy the key from the confirmation window. Squarespace will not show it again.
Developer API Keys
Your new key
Keys stay valid for as long as the site is active.
Paste the key into PopMCP
Open the Squarespace connector in PopMCP, paste the value into API Key, and save.
Connect in PopMCP
Open your workspace, choose Squarespace in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API Keysecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Squarespace immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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
Why: 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
Why: 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
Why: 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
Why: 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
Why: 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.