Squarespace Commerce API
Official vendor OpenAPI document · agent-readyE CommerceOrder Managementoauth227 EndpointsREST
For Agents
Manage inventory, orders, products, profiles, and transactions on Squarespace merchant sites. Provides 27 endpoints for commerce operations including fulfillment creation and webhook subscriptions.
Use for: I need to retrieve all unfulfilled orders from a Squarespace store, Adjust the inventory count for a specific product variant, Create a fulfillment with tracking number for a shipped order, List all products in a Squarespace store with their variant details
Not supported: Does not handle website content management, domain configuration, or page building - use for commerce operations (orders, inventory, products) only.
Control commerce operations on Squarespace merchant sites - inventory adjustments, order retrieval and fulfillment, product and variant management, customer profiles, transaction history, and webhook subscriptions - through 27 REST endpoints. Enables external integrations for fulfillment providers, accounting tools, and inventory management systems to sync with Squarespace storefronts.
Install Jentic One Beta
Connect the Squarespace Commerce API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Squarespace Commerce API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquarespace.com%2Fsquarespace" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsquarespace.com%2Fsquarespace" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Squarespace Commerce API.
Adjust inventory quantities for specific product variants with increment and decrement operations
Retrieve and filter orders by fulfillment status, modification date, and customer email
Create fulfillment records with carrier tracking information for shipped orders
Query product catalogs with variant-level pricing, SKU, and stock data
Access customer profiles and transaction histories for merchant accounting integrations
Subscribe to commerce webhooks for real-time order and inventory change notifications
Use Cases
Patterns agents use Squarespace Commerce API for, with concrete tasks.
★ AI Agent Order Fulfillment
AI agents use the Squarespace Commerce API through Jentic to automate fulfillment workflows. An agent can poll for new orders, mark them as shipped with carrier and tracking details, and subscribe to webhooks for real-time order notifications - removing manual intervention from the fulfillment pipeline for Squarespace merchants.
Retrieve all orders with fulfillment status 'PENDING' from the last 48 hours, then create a fulfillment for order ID abc123 with carrier 'UPS' and tracking number '1Z999AA10123456784'
Inventory Synchronization
Synchronize Squarespace inventory levels with external warehouse management or ERP systems. The inventory endpoints support both individual variant adjustments and bulk quantity queries. Retrieve current stock for all variants, push updated quantities after warehouse counts, and set up webhooks to capture real-time stock changes from Squarespace-side sales.
Retrieve the current inventory quantity for variant ID var_456 and then adjust it by -5 units to reflect a warehouse shipment
Product Catalog Export
Export Squarespace product catalogs for use in marketplace listings, comparison shopping feeds, or print catalogs. The products endpoint returns all products with their variants, pricing, images, and SKUs. Paginate through the full catalog and transform the data for external channel distribution or reporting dashboards.
List all products in the store with pagination, extracting each product's title, price, SKU, and variant count for a CSV export
Accounting and Transaction Reconciliation
Pull transaction records from Squarespace for bookkeeping and reconciliation. The transactions endpoint returns payment details including amounts, fees, and payment methods. Match transactions to orders for revenue reporting, feed data into accounting tools, and track refunds or chargebacks across the merchant's financial records.
Retrieve all transactions from the last 30 days and calculate total revenue by summing transaction amounts minus fees
Key Endpoints
27 endpoints — control commerce operations on squarespace merchant sites - inventory adjustments, order retrieval and fulfillment, product and variant management, customer profiles, transaction history, and webhook subscriptions - through 27 rest endpoints.
METHOD
PATH
DESCRIPTION
GET
/commerce/orders
List orders with filtering by status and date
POST
/commerce/orders/{orderId}/fulfillments
Create a fulfillment with tracking details
GET
/commerce/products
List all products with variant details
GET
/commerce/inventory
Retrieve inventory quantities for all variants
POST
/commerce/inventory/adjustments
Adjust inventory quantities for variants
GET
/commerce/transactions
List transaction records with payment details
POST
/webhook_subscriptions
Create a webhook subscription for commerce events
GET
/commerce/profiles
List customer profiles
GET
/commerce/orders
List orders with filtering by status and date
POST
/commerce/orders/{orderId}/fulfillments
Create a fulfillment with tracking details
GET
/commerce/products
List all products with variant details
GET
/commerce/inventory
Retrieve inventory quantities for all variants
POST
/commerce/inventory/adjustments
Adjust inventory quantities for variants
GET
/commerce/transactions
List transaction records with payment details
POST
/webhook_subscriptions
Create a webhook subscription for commerce events
GET
/commerce/profiles
List customer profiles
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Squarespace Commerce API by hand means running its OAuth 2.0 flow against api.squarespace.com/1.0, refreshing tokens, and managing webhook subscriptions yourself. Through Jentic you install once, import the Squarespace Commerce API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
You can limit the agent to the operations it needs, such as listing orders, reading inventory, or listing products, so it stays on commerce reads and never fulfills an order or adjusts inventory unless you add those operations.
Credential isolation
Your Squarespace OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list recent orders' or 'fulfill an order with tracking', and Jentic returns the matching Commerce API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Advanced payment processing and subscription billing beyond Squarespace's built-in payments
Use when the merchant needs payment features not available through Squarespace Payments, such as multi-party payouts, metered billing, or advanced fraud detection.
FAQs
Specific to using Squarespace Commerce API through Jentic.
What authentication does the Squarespace Commerce API use?
The Squarespace Commerce API uses OAuth 2.0 bearer tokens. Applications must complete the OAuth flow to obtain an access token scoped to the merchant's site. Through Jentic, your OAuth tokens are stored encrypted in your Jentic One instance - agents receive pre-authenticated requests without managing token refresh or authorization flows.
Can I create order fulfillments with tracking information?
Yes. POST to /commerce/orders/{orderId}/fulfillments with a body containing the carrier name (e.g., 'UPS', 'FedEx'), tracking number, and optionally the ship date. The order status updates automatically once a fulfillment is created.
What are the rate limits for the Squarespace Commerce API?
Squarespace enforces a rate limit of 40 requests per second per OAuth token and 200 requests per second per site across all tokens. Exceeding limits returns a 429 response with a Retry-After header. Jentic handles automatic backoff and retry for rate-limited requests.
How do I sync inventory levels with an external system through Jentic?
Search Jentic for 'adjust Squarespace inventory' to discover the POST /commerce/inventory/adjustments operation. Pass an array of variant quantity adjustments (increment or decrement). For initial sync, use GET /commerce/inventory to retrieve current levels for all variants, then push deltas as stock changes occur.
Can I filter orders by fulfillment status?
Yes. The GET /commerce/orders endpoint supports a fulfillmentStatus query parameter with values like PENDING, FULFILLED, and CANCELED. Combine with modifiedAfter and modifiedBefore date filters to retrieve specific order subsets for processing.
Does the API support webhook notifications for new orders?
Yes. POST to /webhook_subscriptions with a topic (e.g., 'order.create', 'inventory.update') and an endpointUrl. The API sends HTTP POST callbacks to your URL when the specified commerce events occur. Use GET /webhook_subscriptions to list active subscriptions.
Can I limit what my agent is allowed to do with the Squarespace Commerce API?
Yes. Because Jentic One is self-hosted, you decide which Squarespace Commerce operations your agent may call, and your own rules govern access. You can restrict it to read-only commerce work such as listing orders with GET /commerce/orders, reading stock with GET /commerce/inventory, and listing products, so it never creates a fulfillment or posts an inventory adjustment unless you explicitly add those operations. The OAuth credentials stay in your Jentic One instance and are injected only for the operations you have allowed.
GET STARTED