PPlatformAppStores

Squarespace Extensions

Ecommerce

Squarespace, Inc. · Ecommerce & storefront platforms

Best for: SaaS builders offering an external service (marketing, shipping, sync) that integrates with design-led Squarespace commerce stores via OAuth.

Overview

Squarespace Extensions is a curated marketplace of third-party integrations that connect to Squarespace Commerce sites — predominantly shipping, fulfillment, inventory, accounting, and marketing connectors. Unlike embedded-UI marketplaces, Extensions are primarily external services that authenticate into a merchant's store via the Squarespace Commerce APIs (Orders, Inventory, Products, Transactions) and sync data, rather than rendering deep UI inside the Squarespace editor.

The integration model is strict on auth: public Extensions are required to use OAuth 2.0. A developer applies to become an official Squarespace developer partner and, once approved, receives credentials to authorize against the Commerce APIs, which makes the marketplace curated rather than open. Squarespace does not run a first-party billing rail for Extensions, so the Extension provider is the merchant of record and bills the customer directly. Choose Squarespace Extensions when your product already has its own billing and you want distribution to design-focused commerce merchants through a vetted connector.

How to build & ship

  1. 1Apply to become a Squarespace developer partner and start the OAuth client registration form
  2. 2Receive your reviewed client_id/client_secret and implement the OAuth 2.0 authorization flow
  3. 3Build your integration against the Squarespace Commerce APIs (Orders, Products, Inventory, Transactions)
  4. 4Handle token refresh and scoped permissions for accessing merchant store data
  5. 5Submit the extension for listing in the curated Squarespace Extensions marketplace

Key APIs & SDKs

Commerce APIs (Orders, Products, Inventory)
OAuth 2.0
Transactions API
Webhooks
Profiles API

Integration types

Connector
Extension

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key
  • Security review: Required
  • Public Extensions require applying to become an approved developer partner and passing a gated OAuth-credential approval; listings are curated.
  • Squarespace vets partners at OAuth-client registration and curates marketplace listings, reviewing the integration and its API usage against partner requirements; approval is gated and application-based.
  • Commerce APIs enforce documented rate limits (429 on exceed); specific per-endpoint values vary.
Auth docs Store policies

Monetization

Free
Paid app
Onboarding
$0 to apply (approval required)
Commission
No first-party rev-share; developers bill customers on their own platform
Merchant of Record
Developer is MoR

Pros & cons for builders

Pros

  • Curated, low-competition marketplace so listed extensions get real visibility
  • Clean, standard OAuth 2.0 + REST commerce APIs are straightforward to integrate
  • Design-conscious merchant base receptive to polished, focused tools

Cons

  • Must be approved as a developer partner before you can even build a public extension
  • Narrower commerce API surface and smaller store count limit deep or high-volume use cases

Frequently asked questions

How do I get my app approved on Squarespace Extensions?

Squarespace vets partners at OAuth-client registration and curates marketplace listings, reviewing the integration and its API usage against partner requirements; approval is gated and application-based.

What authentication does Squarespace Extensions use?

Squarespace Extensions apps primarily authenticate with OAuth 2.0, also supporting API key.

How is Squarespace Extensions monetized?

Squarespace Extensions supports Free, Paid app. Typical commission: No first-party rev-share; developers bill customers on their own platform. Onboarding fee: $0 to apply (approval required).

Is a security review required to list on Squarespace Extensions?

Yes, Squarespace Extensions requires a formal security or listing review before apps go live. Public Extensions require applying to become an approved developer partner and passing a gated OAuth-credential approval; listings are curated.