Shoprocket

Shoprocket is an embeddable e-commerce layer for any website. Agents manage products, orders and customers, read shipping and tax settings, and react to store events as they happen.

1 trigger 76 actions API key available

Shoprocket website Vendor Site Capability data verified 2026-08-26

A client signs off their product sheet and the store build flow starts

Agent reads the catalog rows from the sheet the client already maintains

Every row is checked for a name and an existing category, both of which Shoprocket requires at create time

Create Category and Create Product write the catalog, and Create License Keys loads the codes for any digital item

Get Store reports which environment the store is in, and List Shipping Methods confirms at least one method exists to check out against

The agent posts the build summary and the counts it wrote to the account team

The account manager approves the switch to live, and only then does Update Store Mode run

What This Integration Enables

Shoprocket sells to people who already have a site and do not want a second one. The store is an embed, which makes it a natural fit for agencies and for teams whose commerce is a section of a larger property rather than the whole property. The API reflects that: alongside the usual catalog, orders and customers, it will provision a store for a client, invite the team, and hand back a session link straight into the dashboard.

FlowRunner agents keep the catalog in step with a spreadsheet or a product system, react to a paid order, move an order through payment and fulfillment status from a warehouse signal, load and audit license keys for digital goods, and run dated promotions for a campaign. Two properties of this API shape how those agents are built. Creates are issued as PUT and updates as POST, inverted from almost every other vendor, which the connectors layer absorbs so a flow never has to think about it. And several resources are read and delete only, with no create or update route at all, which is why human-in-the-loop sits in front of those deletions rather than behind them.

Without FlowRunner

Every store build is hand assembly The same launch checklist is worked through by hand for each client, and the checklist lives in somebody's head

Some objects can be destroyed but not rebuilt Shipping methods, zones and automatic discounts can be deleted through the API and only recreated in the dashboard

Go live is a moment of nerve Somebody flips the store to live and finds out afterwards whether catalog, shipping and tax were all in place

With FlowRunner

Builds run from the client's own source Catalog, categories and customers are written from the sheet or product system the client already keeps current

Deletes with no inverse are held back An agent never removes an object the API cannot recreate; it presents the case and waits

Go live is a reviewed step The agent assembles the evidence, a person approves, and the switch to live is one deliberate call

Use Case Scenarios

A client store built from the sheet the client already keeps

The account team maintains one sheet per client. The agent reads it with Google Sheets, drops rows missing a name or naming a category that does not exist yet, calls Create Category for the missing ones, then Create Product for each row and Update Product for rows that already have an id recorded. Digital items get their codes through Create License Keys in bulk. When the pass finishes, the agent posts the created and skipped counts to Slack with the rows it refused and why, so the account manager fixes the sheet rather than the store.
Digital fulfillment with an auditable trail of which order consumed which key

An order for a digital product completes. The On Shoprocket Event trigger fires, the agent calls Get Order for the full record, and List License Keys reads the pool for that product. It checks how many unassigned keys remain and, when the pool is running low, calls Create License Keys with the next block from the vendor's file before the pool empties. Update License Key records the assignment against the order, and Get Store Stats feeds the weekly report. Nobody discovers an empty key pool by reading a customer complaint.
An order moved by the warehouse rather than by a person

The warehouse reports a shipment. The agent calls Update Order to set both the payment and the fulfillment status, because Shoprocket documents both as required on that route even when only one is changing, and lets the call email the customer with the text the account team wrote. When the warehouse reports a cancellation instead, the same operation can return the canceled items to stock. That option is the one an agent does not choose alone, because restocking a physical item that was never returned puts a number on a shelf that is not there.

Human-in-Loop Highlight

Update Store Mode is the highest impact call in this connector, and it does not look like it. Test and live are separate worlds in Shoprocket: separate orders, separate customers, separate payment gateways, separate invoice counters, separate webhooks. Switching the mode changes what every other operation in the flow can see, so an agent that flips a live store into test does not break anything loudly, it simply starts reading an empty store and reporting that there were no orders today. So the agent never makes the call on its own. At the end of a build it posts what it verified: the product and category counts, whether a shipping method and a tax rule exist, which gateway is configured, and which mode the store is in right now. The account manager reads that and approves the switch. The agent does the assembly. The person decides when the store starts taking real cards.

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

76 actions

Products

List Products Lists the store's products with optional full text search, sorting, category, id or slug filters and paging. Each row carries the product's categories, media, SKUs, variations, options and review summary, so a single call is usually enough to sync a catalog.
Get Product Retrieves a single product with its categories, media, files, SKUs, variations, options, tabs and review summary. Shoprocket answers this route with a one-element array under data rather than an object, so read data[0] rather than data.
Create Product Creates a product in the store. Name and at least one category are required, and the category must already exist. Shoprocket creates with an HTTP PUT rather than a POST, which is inverted from the usual convention; this operation issues the PUT the vendor expects.
Update Product Updates a product and, in the same call, any number of its SKU variations. Shoprocket documents Name and Categories as required on an update too, so send them even when they are unchanged.
Delete Product Deletes a product permanently, together with its media, license keys and SKU variations. This cannot be undone.
List Product Media Lists the images, videos and audio attached to a product, optionally narrowed to one media type. Shoprocket has no upload route on this API, so media is added in the dashboard and read back here.
Create Shipment Categories Attaches customs shipment categories to a product, each one a slug, a harmonized system code and a display name. These drive customs paperwork for cross border shipping.

License Keys

List License Keys Lists the license keys attached to a digital product, optionally narrowed to used or unused keys. Each row names the order that consumed the key, so this is how you audit which customer received which key.
Get License Key Retrieves a single license key by its id, showing the key itself, its used or unused state and the order that consumed it.
Create License Keys Adds one or more license keys to a digital product in a single call. Keys are added as unused and are handed to customers in the order they were created.
Update License Key Changes a license key's value, its used or unused state, or both. Marking a key unused returns it to the pool and it can then be handed to another customer.

Customers

List Customers Lists the store's customer records with paging. Each row carries the marketing opt in flag and the source that created the customer, which distinguishes a checkout customer from one added through this API.
Get Customer Retrieves a single customer record by id, including the email address, contact number, company, tax number and marketing opt in state.
Create Customer Creates a customer record from an email address, with optional name, contact number, company, tax number and marketing opt in. Shoprocket creates with an HTTP PUT rather than a POST, and the create route names its fields customer_email and customer_name while the update route names the same two fields email and name; this service maps both for you.
Update Customer Updates a customer's email, name, contact number, company, tax number or marketing opt in state. Shoprocket updates with an HTTP POST rather than a PUT, and this route spells its fields email and name where the create route spells them customer_email and customer_name.
Delete Customer Deletes a customer record. Their past orders remain in the store, but the customer record they were placed against is gone.

Orders

List Orders Lists orders with filters for payment method, payment status, fulfillment status, customer, amount range, discount and sale participation, plus free text search across order id, amount, customer name, email, dates and statuses.
Get Order Retrieves a single order with its line items, addresses, totals, tax breakdown, payment payload and applied discounts. Every amount is a decimal string in major units and every flag is the string "0" or "1", so is_unread of "0" is truthy in JavaScript.
Update Order Sets an order's payment and fulfillment status, optionally emailing the customer with custom text and returning canceled items to stock. Shoprocket documents both statuses as required on this route, so send both even when only one is changing, and there is no create or delete route for orders because they originate in the storefront.

Marketing

List Discount Codes Lists the store's coupon codes with paging. Each row carries its usage limit alongside the usage count so far, which is how you spot a code about to run out.
Get Discount Code Retrieves a single discount code by id, including its type, value, what it applies to, its usage limits and its active window.
Create Discount Code Creates a coupon code that is a fixed amount, a percentage or free shipping, applied to all orders, orders over a value, selected products or selected categories.
Update Discount Code Changes a discount code's type, value, targets, limits, active window or enabled state. Shoprocket documents Coupon Type, Value, Description and Applies To as required on an update too, so send them even when unchanged.
Delete Discount Code Deletes a discount code. Orders that already used it keep their recorded discount, but the code stops working immediately.
List Automatic Discounts Lists the discounts that apply without a code, including buy X get Y and spend threshold rules. This resource is read and delete only on the API: Shoprocket publishes no create or update route, so an automatic discount has to be built in the dashboard.
Get Automatic Discount Retrieves a single automatic discount by id, including its buy and get conditions and its active window.
Delete Automatic Discount Deletes an automatic discount so it stops applying at checkout. There is no create or update route for this resource, so a discount deleted here can only be rebuilt in the Shoprocket dashboard.
List Sale Promotions Lists the percentage sales running against all items, selected products or selected categories, with their active windows.
Get Sale Promotion Retrieves a single sale promotion by id, including its percentage, what it applies to and its active window.
Create Sale Promotion Creates a percentage sale across all items, selected products or selected categories, optionally within a date window. Shoprocket has no update route for a sale, so changing one means deleting it and creating a replacement, and the two dates are all or nothing.
Delete Sale Promotion Deletes a sale promotion so its discount stops applying. Since Shoprocket publishes no update route for sales, this plus Create Sale Promotion is how a sale is changed.

Shipping and Tax

List Shipping Methods Lists the store's shipping methods with their rate tables and the regions each one covers. This resource is read and delete only on the API: Shoprocket publishes no create or update route, so shipping methods have to be built in the dashboard.
Get Shipping Method Retrieves a single shipping method by id, including its price type, base price, weight allowance, overcharge price and rate table.
Delete Shipping Method Deletes a shipping method together with all of its rates. There is no create or update route for this resource, so a method deleted here can only be rebuilt in the Shoprocket dashboard, and a store left with no shipping method cannot take a delivered order.
List Zones Lists the geographic zones the store uses to scope shipping and tax rules, each with the continents it links to. This resource is read and delete only on the API.
Get Zone Retrieves a single zone by id with its countries and states expanded. The list route returns linked_continents as a JSON string while this route returns it as a real object, so a flow that reads both has to handle each shape.
Delete Zone Deletes a zone together with the regions inside it. Any tax rule scoped to that zone loses its scope, so check List Taxes before deleting a zone a tax depends on.
List Taxes Lists the store's tax rules with their rates, what they apply to and whether they are inclusive or exclusive.
Get Tax Retrieves a single tax rule by id. Shoprocket echoes tax_applies_to back as a numeric code rather than the word it was created with, so do not expect a round trip of the value you sent.
Create Tax Creates a tax rule with a percentage rate, applied to the subtotal, the subtotal plus shipping, or all orders, and optionally scoped to specific zones.
Delete Tax Deletes a tax rule so it stops being charged. Since Shoprocket publishes no update route for taxes, this plus Create Tax is how a rate is changed.

Store

Get Store Retrieves the store the API key belongs to, with its name, registered name, address, environment, paused state and both publishable keys. Use this as the connection test: it needs no input and fails clearly on a bad key.
Get Store Stats Retrieves sales, order and traffic statistics for a date range, including the daily series used to draw the dashboard graphs and a comparison against the preceding period.
Get Subscription Retrieves the store's own latest Shoprocket plan subscription, with its plan name, billing period, card summary and status. This is the store's bill from Shoprocket, not a customer subscription.
List Payment Gateways Lists the payment gateways configured on the store, with their display names, types, environments and enabled state. The gateways are environment specific, so a store in test mode lists its test gateways.
Get Payment Gateway Retrieves a single payment gateway by id, including its type, description and enabled state.
List Product Filters Lists the storefront product filters, the facets shoppers use to narrow a catalog, with their names and slugs.
Get Product Filter Retrieves a single storefront product filter by id, optionally expanding the values shoppers can pick from.
List Store Texts Lists every storefront string for one language as a flat map of key to translated text, which is how you audit or export a store's wording for a locale.

Store Settings

Update Checkout Settings Sets everything about the checkout form. That covers the terms and conditions checkbox and where its text comes from, the marketing opt in, and which of billing address, contact number and company name are collected and required. It also covers the discount and notes fields, the minimum order value, the post purchase redirect and the seller charge.
Update Branding Settings Turns the Shoprocket logo in the storefront and in customer emails on or off. Removing the branding is a paid plan feature, so a store on a lower plan has the change refused.
Update Digital Download Settings Sets how long a digital download link stays valid after an order is placed. A customer who follows an expired link has to be sent a new one, so this is the setting that decides how much support a digital store generates.
Update Store Mode Switches the store between test and live mode. This is the highest impact setting on the API: the two modes hold separate orders, customers, payment gateways, invoice counters and webhooks, so switching changes what every other operation sees, and switching to live means real cards are charged.
Update Tracking Settings Configures the store's analytics and advertising trackers and which storefront events each one reports. Shoprocket takes the whole tracker list as a JSON array and replaces what it holds, so a call carrying one tracker turns the others off; send every tracker you want to keep.
Update Invoice Settings Sets the invoice number prefix and suffix, the invoice counter for the chosen environment, whether invoices are attached to the order confirmation email and whether product images appear on them.
Update Store Details Sets the store's name, registered business name, address, hostnames, subdomain, order number format and counter, low stock threshold and abandoned cart interval.
Update Locale Settings Sets the store's languages and currencies, which of each is the default, the timezone and the weight and dimension units. Both lists replace what the store holds, and Shoprocket requires the default to be one of the values in its own list, so send the full set every time.

Team

List Team Members Lists everyone with access to the store, with their role, verification state and whether the invitation has been accepted. The id in each row is the store invitation id, which is what the update and remove operations take, not the user id in the same row.
Invite Team Member Sends a store invitation to an email address with a role of admin, edit or read only. The response carries no id, so call List Team Members afterwards to read the invitation id back.
Update Team Member Changes an existing team member's role. Shoprocket updates with an HTTP POST rather than a PUT, and it takes the store invitation id rather than the user id.
Remove Team Member Removes a team member's access to the store, or cancels an invitation that has not been accepted. The person's Shoprocket account is untouched.

Webhooks

List Webhooks Lists the store's webhook endpoints with their URL, signing secret, environment, event count and consecutive failure count. The failure count is the field to watch: it is how you find an endpoint Shoprocket has stopped trusting.
Get Webhook Retrieves a single webhook endpoint by id, with its signing secret and its subscribed events. The events come back in two different shapes across the API: this route has returned them as a plain array of names, while Create Webhook and Update Webhook return them as an array of objects carrying an id and a webhook_event.
Create Webhook Registers a URL to receive store events and returns the endpoint's signing secret in the create response. Shoprocket creates with an HTTP PUT rather than a POST, which matters more here than anywhere else: a POST to this collection is not a route, so a hand rolled registration silently does nothing.
Update Webhook Changes a webhook's URL, its subscribed events or its environment. The event list replaces what the endpoint was subscribed to, so include every event you want to keep.
Delete Webhook Deletes a webhook endpoint together with all of its event subscriptions. Its signing secret cannot be recovered afterwards, so a replacement endpoint gets a new one.
Resend Webhook Log Replays a single past delivery from a webhook's log, which is how you recover an event your endpoint missed while it was down.

Partners

Create Partner Session Creates an authenticated session for one of a partner's users against one of their stores, which is how an agency drops a client straight into the Shoprocket dashboard without a second login.
Reactivate Partner User Reactivates a deactivated user on one of a partner's stores, restoring their access. This needs the Partner Key rather than the Store Secret Key.
Create Partner Store Provisions a whole new Shoprocket store under a partner account, with its address, subdomain, units, plan and staff notification addresses. This needs the Partner Key rather than the Store Secret Key, and Shoprocket creates with an HTTP PUT rather than a POST.
Create Partner Team Member Adds a team member to one of a partner's stores, creating the Shoprocket user account in the same call when a password is supplied.

Triggers

1 triggers

Event Triggers

On Shoprocket Event Fires when an order, a customer or a product is created, updated or deleted in the store. Pick one of the nine events, or subscribe to all of them and branch in the flow.

Frequently Asked Questions

What can FlowRunner do with Shoprocket?

FlowRunner agents can run List Products, Get Product, and Create Product in Shoprocket, plus 73 more actions.

Does connecting Shoprocket to FlowRunner require OAuth?

No. Shoprocket connects to FlowRunner with an API key, no OAuth flow required.

Can Shoprocket trigger a FlowRunner workflow automatically?

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

Start building with Shoprocket

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us