Skip to content

t1k:web:commerce:squarespace

FieldValue
Modulecommerce
Version1.9.0
Effortmedium
Tools

Keywords: api, commerce, ecommerce, inventory, orders, products, profiles, squarespace, transactions, webhooks

/t1k:web:commerce:squarespace
[api] [operation]

Integrate a Squarespace store from your own backend: read/write the catalog, keep stock in sync, ingest orders from third-party sales channels, and reconcile payments. All facts here are grounded in the official docs at developers.squarespace.com (verified 2026-07-17) — see the per-API references for endpoint tables and examples.

  • Build a custom app/integration against a Squarespace Commerce Advanced store (API keys) or a multi-site Squarespace Extension (OAuth).
  • Sync products/inventory to or from another system (ERP, POS, marketplace).
  • Import orders created on an external channel (Instagram, a marketplace) into Squarespace.
  • Pull transactions for finance reconciliation.
  • Subscribe to store events via webhooks (OAuth only).
You need to…Go toKey endpoint(s)
Auth, headers, pagination, errors, rate limits, idempotencyreferences/conventions.md(cross-cutting)
Read/write catalog products + variants + imagesreferences/products-inventory.mdGET/POST /v2/commerce/products
Read stock, adjust quantitiesreferences/products-inventory.mdGET /1.0/commerce/inventory, POST /1.0/commerce/inventory/adjustments
List/read/create orders, mark fulfilledreferences/orders-transactions.mdGET/POST /1.0/commerce/orders, POST …/fulfillments
Reconcile payments / payouts / refundsreferences/orders-transactions.mdGET /1.0/commerce/transactions
Read customer profilesreferences/profiles-webhooks.mdGET /1.0/profiles
Subscribe to store events (OAuth only)references/profiles-webhooks.mdWebhook Subscriptions API
  1. Version is per-API, not uniform. Products is v2 (/v2/commerce/products); inventory, orders, transactions, profiles, webhooks are 1.0. Never hardcode one version across all calls. (Since 2025 Squarespace uses integer versioning — a bump means a breaking change.)
  2. User-Agent is required on every request. Requests without a descriptive User-Agent are rejected, and default/library UA strings attract stricter rate limiting. Set a custom one.
  3. API keys can’t do webhooks. The Webhook Subscriptions API is OAuth-only. API keys (Commerce Advanced plan, generated in the site UI) cover everything else. Order creation is also rate-limited to 100/hour on API-key auth (not on OAuth).
Terminal window
curl https://api.squarespace.com/1.0/commerce/inventory \
-H "Authorization: Bearer $SQUARESPACE_API_KEY" \
-H "User-Agent: MyApp/1.0 ([email protected])"

Auth model, scopes, pagination, error shape, and idempotency: references/conventions.md.

The1Studio ships a working MCP server that wraps these APIs (Python/FastMCP): The1Studio/squarespace-mcp — read its client.py/server.py for a concrete, tested httpx client (Bearer + User-Agent, cursor pagination, idempotency keys, lazy key check).

  • references/conventions.md — base URL, versioning table, auth (API key + OAuth), headers, pagination, errors, rate limits, idempotency.
  • references/products-inventory.md — Products API (v2) + Inventory API endpoint tables, response shapes, examples.
  • references/orders-transactions.md — Orders API + Transactions API endpoint tables, create/fulfill bodies, examples.
  • references/profiles-webhooks.md — Profiles API + Webhook Subscriptions API + brief note on Contacts/Discounts/Forms.