Reference · built on requestConnectorCommerce & orders

Squarespace

Orders, inventory, transactions, and order webhooks from a Squarespace site through the Commerce APIs.

Request accessPricing ↗

About

Squarespace is a website builder with a built-in commerce layer. Each site carries orders, inventory, products, and transactions, and the Commerce APIs serve them per site at api.squarespace.com. An order records line items, a shipping address, a fulfillmentStatus, and a paymentState that moves from NOT_CHARGED through PAID to REFUNDED.

Through Fibric, an operator reads new and changed orders, then proposes the next step: fulfil an order with tracking, or adjust a variant's stock. You approve. The connector sends one request and leaves a record: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Squarespace and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Orders through GET /1.0/commerce/orders, filtered by paymentStates such as NOT_CHARGED, AUTHORIZED, PAID, and REFUNDED
  • Order line items, shipping address, fulfillmentStatus, grandTotal, refundedTotal, and channel on each Order
  • order.create and order.update webhook notifications, signed with the Squarespace-Signature header
  • Inventory items through the Inventory API: variantId, SKU, quantity, and whether stock is unlimited
  • Transaction documents through GET /1.0/commerce/transactions: payments, Squarespace-initiated refunds, and gateway errors per order

Proposed actions

  • Target capability: propose fulfilling an order through POST /1.0/commerce/orders/{id}/fulfillments, with carrierName, service, trackingNumber, trackingUrl, and shipDate
  • Target capability: propose a stock adjustment through the Inventory API's adjust endpoint, as an increment, decrement, set-finite, or set-unlimited operation

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Tracking on every fulfilment

    When your carrier creates a label, the operator proposes a fulfilment on the Squarespace order with the tracking number and shouldSendNotification set. You approve. A 409 means the order was already fulfilled.

    With Tracking Sync

  • Hold a suspect order

    order.create arrives. The operator compares the shipping address, totals, and paymentState against your rules and flags orders to check before anyone fulfils them.

    With Order Risk

  • Keep stock counts true

    When a sale elsewhere consumes a variant, the operator proposes a decrement operation for that variantId so the site stops selling what you no longer hold.

    With Oversell Watch

  • Answer a delivery question

    A customer asks where their order is. The operator reads the order's fulfilments and tracking and drafts a reply from that record for a person to send.

    With WISMO Deflection

Requirements

  • A Squarespace site on the Commerce Advanced plan for a custom app with API keys; OAuth extensions work on any plan
  • An API key created under Settings > Advanced > Developer API Keys, with Orders and Inventory set to Read and Write
  • OAuth credentials if you want webhooks: the Webhook Subscriptions API rejects API keys
  • An HTTPS endpoint that checks the Squarespace-Signature header with the subscription secret
Authentication
A site API key or an OAuth access token sent as Authorization: Bearer, with a User-Agent header on every request.

Limits

  • 300 requests per minute. Exceeding it returns 429 with a one-minute cooldown. Create Order with an API key is capped at 100 per hour.
  • The Orders API documents list, get, create, and fulfil. Refunds made outside Squarespace, for example in Stripe, do not appear in Transactions.
  • The Inventory API covers physical products and services only, not gift cards or downloads, and does not return variant attributes such as size or color.
  • The Profiles API is in maintenance mode; customer records come through the Contacts API instead.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Squarespace ↗

Questions and answers

Can I get order webhooks with an API key?
No. The Webhook Subscriptions API needs an OAuth access token; API keys are not supported. Order topics also require OAuth permission for the Commerce Orders API. Subscriptions never expire, and a site lists up to 25 of them.
What are the rate limits?
300 requests per minute, about five per second. Over that, Squarespace returns 429 Too Many Requests with a cool-down of one minute. Create Order with API key authentication is further limited to 100 requests per hour.
Which payment gateways appear in Transactions?
SQUARESPACE, STRIPE, PAYPAL, and SQUARE. Each transaction Document holds the order's payments, refunds made in Squarespace, and gateway errors. Refunds issued directly in a gateway are not captured.
Ask about Squarespace

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Squarespace through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy