Squarespace Orders API

The Squarespace Orders API provides access to order history for a Squarespace merchant site, supporting both one-time purchases and subscription orders. Developers can retrieve, create, and manage orders, as well as import orders from third-party sales channels into Squarespace.

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /1.0/commerce/orders List and filter orders (1.0) · List orders #
Ask an LLM
“How do I list orders for one customer with the versioned 1.0 orders API?”
“Can I filter 1.0 orders by fulfillment status or payment state?”
Tell an agent
List 1.0 orders for customer {customerId}.
List 1.0 orders with fulfillment status {fulfillmentStatus} and payment states {paymentStates}.
POST /1.0/commerce/orders Import a third-party channel order (1.0) · Create order #
Ask an LLM
“How do I import an order placed on another sales channel into my store through the 1.0 API?”
“Can a 1.0 imported order skip deducting stock or skip the customer fulfillment email?”
Tell an agent
Import 1.0 order {externalOrderReference} from {channelName}, placed {createdOn}, items {lineItems}, total {grandTotal}, key {idempotencyKey}.
Create a 1.0 order for {customerEmail} from {channelName} with inventory behavior {inventoryBehavior}.
GET /1.0/commerce/orders/{id} Get one order (1.0) · Get order #
Ask an LLM
“How do I look up a single order by ID on the versioned 1.0 API?”
“What does a 1.0 order record contain?”
Tell an agent
Get 1.0 order {id}.
Show the details of order {id} from the 1.0 endpoint.
POST /1.0/commerce/orders/{id}/fulfillments Mark an order fulfilled (1.0) · Fulfill order #
Ask an LLM
“How do I mark an order as shipped with the 1.0 fulfillment endpoint?”
“Is the customer email optional when fulfilling an order through version 1.0?”
Tell an agent
Fulfill 1.0 order {id} with shipments {shipments}.
Mark 1.0 order {id} fulfilled, notify customer: {shouldSendNotification}.
GET /commerce/orders List orders (unversioned) · Retrieve All Orders #
Ask an LLM
“Which orders were updated recently, via the unversioned orders path?”
“Can the unversioned order listing be filtered by fulfillment status?”
Tell an agent
Retrieve unversioned orders modified after {modifiedAfter}.
Retrieve unversioned orders with fulfillment status {fulfillmentStatus}.
POST /commerce/orders Import an order (unversioned) · Create an Order #
Ask an LLM
“Does importing an order through the unversioned path charge the customer's card?”
“What addresses and totals must an unversioned imported order include?”
Tell an agent
Create an unversioned order for {customerEmail} with items {lineItems}, totals {totals}, billing {billingAddress} and shipping {shippingAddress}.
Record external order {externalOrderReference} from channel {channel} for {customerEmail} without the 1.0 prefix.
GET /commerce/orders/{orderId} Get one order (unversioned) · Retrieve a Specific Order #
Ask an LLM
“Can I see the line items, addresses and payment details of an order via the unversioned path?”
“How do I retrieve a specific order without the 1.0 prefix?”
Tell an agent
Retrieve unversioned order {orderId}.
Show line items and payment details for order {orderId} from the unversioned endpoint.
POST /commerce/orders/{orderId}/fulfillments Fulfill line items with tracking (unversioned) · Fulfill an Order #
Ask an LLM
“How do I add tracking numbers when fulfilling an order via the unversioned path?”
“Can I fulfill specific line items through the unversioned fulfillment endpoint?”
Tell an agent
Fulfill unversioned order {orderId} with shipments {shipments}, send notification: {shouldSendNotification}.
Record tracking {shipments} on order {orderId} without emailing the customer ({shouldSendNotification}).

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/squarespace:squarespace-orders-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

squarespace-orders-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Squarespace Orders API
  version: '1.0'
  description: 'Operations tagged Orders across 2 of this provider''s published API definitions: squarespace-commerce-api-v2-openapi.json, squarespace-orders-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.squarespace.com
  description: Commerce API
- url: https://api.squarespace.com/1.0
  description: Production Server
tags:


# --- truncated at 32 KB (51 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/squarespace/refs/heads/main/openapi/squarespace-orders-api-openapi.yml