Commerce & Payments · Integration
Squarespace
Add Squarespace to your product for your customers, and give your AI agents governed access to it.
Squarespace is the website, and Squarespace Commerce is the store on it, which is the half an integration works with: orders with their line items and fulfilment state, the products and variants behind them, the inventory counts that decide whether something can be sold, and the customer profiles built up from purchases. What catches people out is how narrow and how deliberate the API is. Access is per store through a key or an OAuth grant rather than a general-purpose site API, inventory is adjusted by variant rather than by product, and marking an order fulfilled is a specific write with shipment detail attached rather than a status edit. Limits apply per store, so a first import is paced. fastn holds each seller's credentials and follows the API version.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each seller connect their own Squarespace store so your product reads orders and writes fulfilment back without a manual export.
Adjust inventory by variant, since a size or a colour is what actually runs out rather than the product itself.
Read products and their variants so your product prices and lists exactly what that store sells.
Mark an order fulfilled with its shipment detail, so the buyer gets the notification Squarespace sends rather than one you build.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists unfulfilled orders for a store and explains which are waiting on stock.
An agent updates inventory for a variant within scoped permissions, with the adjustment logged.
An agent answers a question about a buyer's order history from the store's own records.
Example prompt
Which Squarespace orders are still unfulfilled after three days, and is any of them held up by an out of stock variant?
Set up Squarespace in 4 steps
- 01Enable the Squarespace connector in your fastn dashboard.
- 02Have each seller connect their own store, with the API key or OAuth grant their Squarespace plan supports.
- 03Map the order, product, variant and inventory fields your product uses, then enable the fulfilment writes you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Squarespace integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Squarespace integration without building it. Your customers connect their own Squarespace account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Squarespace update is not your on-call problem.
- One integration serves your product and your agents. The same governed Squarespace connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Wix
Shopify
StripeOften used alongside
Tools the same teams tend to run next to Squarespace, across other categories.
NetSuite
Notion
Box
DocusignSquarespace integration FAQ
How do I add a Squarespace integration to my product?
Enable the Squarespace connector in your fastn dashboard, then let each customer authenticate their own Squarespace account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Squarespace client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Squarespace account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Squarespace account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Squarespace integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists unfulfilled orders for a store and explains which are waiting on stock.
Who maintains the Squarespace integration?
fastn does. When Squarespace changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Squarespace integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Squarespace integration?
A common starting point: let each seller connect their own Squarespace store so your product reads orders and writes fulfilment back without a manual export. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Squarespace integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Squarespace does not change your per-connector cost. You can start free with 3 connected accounts.
Add Squarespace to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.