Snipcart

Snipcart is a developer-first shopping cart that drops into any site. Agents manage products, inventory, orders and discounts, read and cancel subscriptions, and react to order events.

1 trigger 47 actions Basic auth available

Snipcart website Platform Documentation Capability data verified 2026-08-26

On Snipcart Event fires for a completed order

Get Order returns the line items, taxes, addresses and any digital goods

List Order Refunds confirms nothing has already been refunded against the order

The order is handed to the warehouse and Update Order writes the tracking number back

Create Order Notification emails the customer the tracking details

Get Order Digital Goods reads the isValid flag on every download link

A person decides whether to reissue a download whose cap is already exhausted

What This Integration Enables

Snipcart is the cart you bolt onto a site you already own, which is a different proposition from a hosted storefront. The catalog is not really in Snipcart. It lives in your own markup, and Snipcart mirrors it by crawling the page. That design keeps the store cheap to build and it puts a handful of small settings, the store domain and the list of domains the widget may run on, in charge of whether the site can sell at all.

FlowRunner agents work the surface that sits around that cart. They read completed orders and push them to a warehouse, write tracking back and email it to the customer, set per variant stock from the system that counts, pull abandoned carts above a value threshold, watch subscription payments for declines, and issue refunds. The operations that end a sale or reach the storefront's configuration are exactly where human-in-the-loop belongs, and the rest can run unattended.

Without FlowRunner

The cart is the only system that knows Money is taken, and the warehouse finds out when somebody forwards the confirmation email

Stock lives in two places Levels sit in the website's markup and in whatever system actually counts the shelf, and the two drift

Store settings have no owner The domain list that decides whether checkout runs at all is edited by hand and remembered by nobody

With FlowRunner

Orders leave the cart by themselves A completed order reaches the warehouse, the tracking goes back onto the order, and the customer is told

One counted source writes stock Per variant levels are pushed from the system that counts, and the out of stock policy travels with them

Settings change with a witness A change to the store domain or the allowed domain list is prepared by the agent and confirmed by a person

Use Case Scenarios

A completed order becomes a shipment without anyone forwarding an email

The On Snipcart Event trigger fires when an order completes. The agent calls Get Order for the full object, checks List Order Refunds so a returned order is never shipped twice, and hands the line items to the warehouse. When the label comes back, Update Order records the tracking number and Create Order Notification emails it to the customer with the delivery method set to Email. A row lands in Google Sheets for the daily reconciliation, and Create Order Log Item leaves an internal note on the order so the next person to open it can see what the agent did and when.
Abandoned carts sorted before anybody chases them

On a schedule the agent calls List Abandoned Carts, pages it with the continuation token, and keeps the carts above a value threshold that were left in the last few hours. It reads the contents of each one with Get Abandoned Cart, drops any cart whose token now returns a 404 because that sale was already recovered, and posts the shortlist to Slack with the customer, the value and the items. A person decides which ones are worth a discount. Only then does the agent call Create Discount for the codes that were approved.
A domain change that does not take checkout down

A store moves to a new hostname, or adds a regional subdomain. The agent reads the current configuration with Get Store Domain and List Allowed Domains, works out the exact set the site will need after the move, and posts the before and after side by side. Nothing is written until a person says go. Once approved, Add Allowed Domains runs first so the new hostname works before anything is taken away, and Remove Allowed Domains runs last. The order matters because the cart widget will not load on a hostname that is not on the list.

Human-in-Loop Highlight

Every other write in this connector affects one order or one product. Update Store Domain and Remove Allowed Domains affect whether the cart runs at all. The domain is normalized to a bare hostname and the protocol falls back to HTTP when it is omitted, so a plausible looking value can quietly stop the widget from loading on the live site. Remove Allowed Domains is all or nothing too. If any domain in the request is not currently on the list, the whole call fails and nothing is removed. So the agent prepares the change and stops. It posts: "Store domain moves from shop.acme.com to www.acme.com over HTTPS. Allowed domains gain checkout.acme.com and lose staging.acme.com. Approve the write?" A person approves, and the agent adds before it removes. The agent is faster at assembling the change. It is not the right party to take the store offline.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

47 actions

Orders

List Orders Lists completed orders with a rich filter set covering status, payment status, date range, invoice number, product, purchaser and eight exact match address fields.
Get Order Returns a single order by token, including its line items, applied promo codes, taxes, addresses, refunds and any withdrawal requests. This is the full object, unlike the Excerpt format available on List Orders.
Update Order Updates a single order's status, payment status, tracking details, addresses, notes, custom fields or metadata. Only the fields you supply are changed.
Update Order Statuses In Batch Changes the status of several orders in one call, taking a list of order token and status pairs. Each change raises the same webhook events and customer notifications as a single update, so a large batch produces a large number of emails.
Get Order Digital Goods Returns the downloadable files attached to an order, each with its download URL, how many times it has been downloaded, its download cap and expiry window, and an isValid flag that is false once the cap is reached or the link has expired.

Order Notifications And Log

List Order Notifications Lists the notifications recorded on an order, most recent first, paged with Offset and Limit. Fields are omitted rather than nulled when empty, so a private comment carries no subject, body or sentOn; only creationDate and type are always present.
Create Order Notification Records a notification on an order and optionally emails it to the customer, which is how Snipcart sends invoices, tracking numbers, shipping updates and comments.
List Order Log Items Returns the comments recorded on an order's log as a bare array, each with its id, date, content and type. The log is the internal comment trail on an order and is separate from the customer facing notifications.
Create Order Log Item Appends an internal comment to an order's log, which is the audit trail your team sees on the order in the dashboard.

Refunds

Create Refund Issues a refund against an order and submits it to the gateway that processed the original payment. This is irreversible, the amount cannot exceed the order's grand total, and taxes are only refunded when Auto Refund Taxes is on.
List Order Refunds Returns every refund issued against an order as a bare array rather than the paged envelope used elsewhere in the API, each entry carrying its amount, comment, creation date and whether the payment gateway processed it.
Get Refund Returns a single refund on an order by its identifier, including the amount, the comment, whether the customer was notified and whether the payment gateway has processed it.

Customers

List Customers Lists the customers on the account, paged with Offset and Limit and filterable by status, exact email, partial billing name and creation date range.
Get Customer Returns a single customer by identifier in the same flat shape as List Customers, including the order count and total order value under statistics, and both addresses as billingAddress and shippingAddress prefixed fields.
List Customer Orders Returns every completed order placed by one customer as a bare array, in the same shape as the Orders API. Orders still in progress are excluded, so an abandoned cart never appears here.
Update Customer Updates a customer's email and addresses. Only email, billingAddress, shippingAddress and cartToken are accepted, and the addresses are nested objects rather than the flat prefixed fields the read routes return.
Delete Customer Permanently deletes a customer account from the store. Snipcart answers with 204 No Content, so this operation reports the outcome and the id rather than a copy of the record.

Products

List Products Lists the products Snipcart has recorded for the store, each with its price, categories, stock, variants and a statistics block carrying the number of sales and total sales value.
Get Product Returns a single product by either its Snipcart GUID or your own user defined ID, including price, stock, inventory management method, custom fields, per variant stock levels and its sales statistics.
Import Products From URL Fetches a URL and imports the products found on it, which is the only way to get products into Snipcart other than completing an order.
Update Product Inventory Sets a product's stock level, inventory management method, per variant stock and out of stock purchase policy. Only those four fields are read; name, price and description live on your own site and are ignored here.
Archive Product Archives a product so it no longer appears in the default product listing. This is not a permanent delete: Snipcart only sets the archived flag, and the product is restored automatically if it is added to a cart again or re-imported from your site.

Discounts

List Discounts Returns every discount on the account as a bare array with no paging, each carrying its trigger, type, code, usage counters, expiry and archived flag.
Get Discount Returns a single discount by identifier, including its trigger and type, the fields those two require, how many times it has been used, how many uses are still sitting in uncompleted carts, and its expiry.
Create Discount Creates a discount, choosing a trigger that activates it and a type that decides what it does. The required extra fields depend on that pair and are checked before the call.
Update Discount Replaces a discount with the definition you send, so include the full object rather than only the fields you are changing. It accepts the same fields as Create Discount plus Archived, and the per trigger and per type requirements are checked before the call.
Delete Discount Permanently deletes a discount. Snipcart refuses with a 400 if the discount has ever been used in a completed order, in which case archive it through Update Discount instead.

Subscriptions

Count Subscriptions Counts the store's V3 subscriptions in one or more states, which is the cheapest way to watch for a rise in cancellations or failed payments.
List Subscriptions Lists the store's subscriptions across both the legacy V1 and the current V3 engines, newest first, filterable by status, date range, customer, plan name and last invoice state.
Get Subscription Returns one subscription with its state, subscriber, billing schedule, next billing date, upcoming payments, gateway id and recurring amount. Version selects the engine, and it matters: Snipcart's own default is the legacy V1, whose identifier is a GUID, while a V3 subscription is identified by its initial order token.
Cancel Subscription Cancels a subscription, which Snipcart exposes as a DELETE even though nothing is deleted. A V1 subscription is canceled with the payment gateway at once, while a V3 subscription moves to CancellationRequested and ends at its next billing date.
List Subscription Invoices Returns the invoices, which are the recurring orders, issued for one subscription, each with its order token, amount, invoice number and paid flag.

Abandoned Carts

List Abandoned Carts Lists carts customers started but never completed, which are the carts still in the InProgress status, with their contents, totals, addresses and email.
Get Abandoned Cart Returns a single abandoned cart by token with its items, discounts, addresses, shipping information and totals. The cart must still be in progress: once the customer checks out, this route answers 404 and the record becomes an order, so a 404 usually means the sale was recovered.

Shipping Methods

List Shipping Methods Returns every manually defined shipping method on the account for the mode the API key belongs to, each with its rate tiers, country and postal code conditions and estimated delivery window.
Get Shipping Method Returns a single custom shipping method by its GUID, with every rate tier and the conditions that gate it. It answers 404 when the id belongs to another account or to the other mode, since a key only ever sees its own mode's data.
Create Shipping Method Creates a named shipping option with one or more rate tiers, which can be graded by order weight in grams and by order total and restricted by country, state or a postal code regular expression.
Update Shipping Method Replaces a custom shipping method with the definition you send, so include every rate tier and condition rather than only the ones you are changing.
Delete Shipping Method Permanently deletes a custom shipping method, which removes that option from checkout at once. Snipcart answers 204 No Content, so this operation reports the outcome and the id rather than a copy of the record.

Store Settings

Get Store Domain Returns the account's default website domain and the protocol it is served over. This is the domain the cart widget is anchored to, not an email sending domain.
Update Store Domain Sets the account's default website domain, the one the cart widget is anchored to. The domain is normalized to a bare hostname, and the protocol falls back to HTTP when it is omitted, so set it explicitly.
List Allowed Domains Returns the extra domains and subdomains the cart widget is permitted to run on, as a bare array of domain and protocol pairs.
Add Allowed Domains Adds one or more domains or subdomains to the list the cart widget may run on, and returns the full updated list rather than only the additions.
Remove Allowed Domains Removes one or more domains from the allowed list, matching on the domain rather than the protocol, and returns the full remaining list.

Sessions And Security

Get User Session Returns a customer session by token together with the customer it belongs to and the session's expiry, which is how a server side flow turns a session token from your storefront into a known customer.
Validate Request Token Checks an inbound webhook's X-Snipcart-RequestToken with Snipcart, which is how a delivery is proven genuine since Snipcart signs nothing. The token is valid for one hour, and a key in the wrong mode reports a genuine delivery as invalid.

Webhooks

Get Webhook Settings Reads the store's configured webhook URLs from an undocumented route whose existence is proven by Snipcart's own route oracle but whose response shape the vendor has never published.

Triggers

1 triggers

Event Triggers

On Snipcart Event Fires on Snipcart's order and subscription events: an order completing, a status, payment status or tracking change, a refund, a notification, a withdrawal request, and a subscription payment succeeding or failing or a subscription being canceled. Deliveries are proven with Snipcart's request token callback rather than a signature, and status and tracking changes arrive with their from, to and tracking fields beside the order.

Frequently Asked Questions

What can FlowRunner do with Snipcart?

FlowRunner agents can run List Orders, Get Order, and Update Order in Snipcart, plus 44 more actions.

Does connecting Snipcart to FlowRunner require OAuth?

No. Snipcart connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Snipcart trigger a FlowRunner workflow automatically?

Yes. Snipcart supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Snipcart

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us