Get the store bound to this API key: name, slug (storeId), tier, domain, currency, configured payment processors, allowed domains. Secrets are never included.

Current plan tier, its limits, and live usage (active products, coupons, monthly orders). Check this before bulk-creating products.

List ALL products including drafts and archived. Optionally filter by status or search by name/slug substring (filtering happens client-side).

List the store’s categories (via the public API).

List orders, newest first. Filter by status and/or ISO date range; paginate with limit/lastKey.

List all coupons with usage counts.

List email subscribers (Product Alerts). Paginate with limit/lastKey.

Get store settings: shipping_config, tax_config, email_config, order_config.

Get hosted-storefront configuration (template, hero, sections). Only meaningful on hosted plans.

Sales report for a date range: revenue, orders, AOV, tax collected (total + by state), shipping, discounts, top products.

Cart funnel analytics for a date range: sessions that viewed, added to cart, reached checkout, purchased; abandoned value.

Recent signed-webhook delivery attempts and results.

Create a product. Defaults to DRAFT (invisible to shoppers) unless status "active". Prices in integer cents. Upload images first with upload_image and pass the returned fileUrls.

Update any fields of an existing product by productId (partial update). Prices in integer cents.

Archive (soft-delete) a product — it disappears from the store but stays in the database. CONFIRM WITH THE USER before calling; name the product, not just the id.

Create a category. parentId makes it a subcategory.

Update a category by categoryId (partial).

Create a coupon. value = 1-100 for percent_off, integer cents for fixed_amount, ignored for free_shipping.

Delete a coupon by code. CONFIRM WITH THE USER before calling.

Update an order’s status, tracking number, or notes. Status transitions to "shipped" notify the customer webhook. Allowed statuses: pending, confirmed, processing, shipped, delivered, cancelled, refunded. NOTE: to actually refund money, the merchant must use the dashboard — this tool only changes the label.

Resend the order confirmation email to the customer for an order.

Upload an image (or digital file) to the store’s storage and get back a public fileUrl for product/category images. Provide EITHER file_path (local server only) OR source_url (fetched server-side).

Update ONE settings key: shipping_config, tax_config, email_config, or order_config. Read get_settings first and send the full desired value for that key. Tier limits apply to shipping methods.

Update store display config: name, domain, brandColor, currency, allowedDomains. Payment credentials can NOT be changed here (dashboard only). Changing allowedDomains affects which sites the widget works on — confirm with the user.

List the store's fulfillment vendors — custom partners (e.g. a local print shop) that get emailed an order sheet when their routed products sell. Metadata only; use get_vendor for the email template HTML. Pro/Expert plans.

Fetch one fulfillment vendor including its order-sheet templateHtml.

Create a fulfillment vendor. Requires name and at least one "to" address. Route products to it afterwards via update_product (fulfillment_vendor_id + vendor_sku). Vendor order emails never include prices. Max 10 vendors per store.

Update a fulfillment vendor (partial — provide only the fields to change; the rest are preserved, including the saved template). Use status "paused"/"active" to pause or resume order emails.

Delete a fulfillment vendor — its routed products keep selling but orders stop being forwarded. CONFIRM WITH THE USER before calling; name the vendor, not just the id.

Email the MERCHANT (never the vendor) a test order sheet rendered with sample data, so they can see exactly what the vendor will receive.

Manually email an existing order to a vendor — for orders placed before the vendor was set up (items match by the products' CURRENT vendor routing) or deliberate re-sends. Orders with routed items are emailed automatically at payment; this is only for manual sends. Note: while the store's Fulfillment Test Mode is on, the email goes to the merchant with a [TEST] banner.