29 Next

29 Next, now trading as Next Commerce, is an ecommerce platform built for direct response and subscription commerce. Agents react to paid orders in real time, run subscription dunning across gateways, manage the catalog, fulfillment and disputes, and drive external checkouts through the Campaigns API.

1 trigger 186 actions API key available

29 Next website Platform Documentation Capability data verified 2026-08-26

On Store Event fires when a subscription payment fails

Get Subscription returns the schedule, the amount and the gateway the charge was routed through

List Subscription Transactions shows how many attempts this cycle has already made, and against which gateways

Retry Subscription Payment runs the next attempt against another gateway in the routing group

The customer is asked to update their card and the dunning channel gets the running count

List Disputes is read for an alert already open against that card

A person decides what happens to a subscription still failing once the routing group is exhausted

What This Integration Enables

29 Next, which now trades as Next Commerce, is built for the kind of commerce where the first sale is the beginning of the money rather than the end of it. That shows in the API. Subscriptions have their own lifecycle with retry, pause, resume and renew. Payments route across gateway groups so a decline can be re-presented somewhere else. Disputes are a first class resource with alerts as well as chargebacks. And a separate Campaigns API drives an external checkout page, including the one click post purchase upsell that charges the card again on the thank you page.

FlowRunner agents work all of it. They react to a paid order and book fulfillment, run dunning across gateways, and keep catalog, prices and stock records in step with a product system. They turn a chargeback alert into a refund before the case lands, recover carts with the shopper's email and contents, and drive a checkout built against the Campaigns API. The API's own vocabulary makes the boundaries clear, and this connector keeps them. Calculate Order Refund is a dry run and Refund Order is not. Add Order Line adds a line and Add Order Line Items charges for it. Pause Subscription is reversible and Cancel Subscription is not. Where the vendor has drawn a line between describing money and moving it, human-in-the-loop sits on the moving side.

Without FlowRunner

Dunning is a monthly export Failed payments are pulled into a sheet and chased in batches, so a card recoverable on day two gets chased on day fourteen

Chargeback alerts sit in an inbox The network alert arrives before the chargeback does, and the refund that would have settled it is decided after the window closes

Post purchase upsells are hand wired The one click upsell on the thank you page is glued together per campaign, and nobody can say later which orders it charged

With FlowRunner

Dunning runs per subscription Each failure is retried against the gateway group on its own clock, with the attempt history read before the next attempt

Alerts become a same day decision An alert is matched to its transaction and put in front of a person while a refund can still resolve it

Extra charges are recorded and reviewed Every charge against a saved card is written with the campaign that caused it, and a person approves before the first one runs

Use Case Scenarios

Dunning that works a card while the card is still worth working

A renewal declines and the On Store Event trigger fires. The agent calls Get Subscription for the amount and the schedule, then List Subscription Transactions to see what this cycle has already tried and where. If the routing group has an untried gateway, Retry Subscription Payment runs there rather than re-presenting to the one that just refused. The customer gets an update card request through Brevo, and the running attempt count posts to the revenue channel in Slack. When the group is exhausted, the agent stops and asks, because canceling is not reversible in this platform and pausing is.
A chargeback alert answered before it becomes a chargeback

An alert feed from the card networks reaches the flow. The agent records it with Create Dispute against the transaction, calls Get Transaction and Get Order for the amount, the products and the customer's history, and Calculate Order Refund to see exactly what a refund would come to including tax and shipping. It posts all of that to finance in one message. If the answer is to refund, Refund Order runs and Resolve Dispute closes the case with the resolution recorded. If the answer is to fight it, Create Dispute Note captures the evidence and the case stays open. Either way the decision was made with the numbers in front of somebody, on the day the alert arrived.
A fulfillment partner that answers instead of being chased

Orders assigned to a third party warehouse show up under List Assigned Fulfillment Orders. The agent sends the work with Send Fulfillment Request and watches for the partner's answer. An accepted request is picked up and Create Fulfillment Order Fulfillment records the shipment and its tracking. A rejection or a hold goes straight to the operations channel with the reason, because a held fulfillment order that nobody looks at is a customer waiting. When stock at a location has run out, List Stock Records filtered to low stock feeds the reorder sheet in Airtable rather than a person noticing next week.

Human-in-Loop Highlight

Add Checkout Order Upsell adds packages to an order that has already been paid for and charges the same payment method again, with no fresh payment step from the shopper. That is what makes a one click upsell one click, and it is also why it is the operation on this connector an agent should not fire on its own judgment. A wrong package, a wrong price, or a rule that fires on the wrong segment does not produce an error. It produces a second charge on a real card, and the customer's first notice of it is a bank line they did not expect. So the agent builds the upsell, prices it with Calculate Checkout Cart, and stops: "Campaign SUMMER-2 would add package 41 at 39.00 USD to order 20418, charging the card ending 4417 again with no new authorization. Approve this rule for the campaign?" Once a person approves the rule, the agent runs it. The digital andon cord is not there because the agent is unreliable. It is there because taking money twice is a decision, not a step.

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

186 actions

Store

Get Store Returns the store's business information and settings, including its available currencies and languages, contact address, timezone and default gateway configuration. This is the cheapest connection test: it needs only the store:read scope and touches no customer data.

Orders

List Orders Lists the store's orders newest first, with filters for free text, order number, status, payment and fulfillment and delivery status, date placed, currency, product or SKU, coupon codes, tags, countries and the full utm and affiliate attribution set.
Get Order Returns a single order with its lines, addresses, totals, payment and fulfillment status, attribution and metadata. Orders are addressed by order number, not by a numeric ID.
Create Order Creates an order directly through the Admin API, with line items, a customer, shipping and billing addresses, shipping cost, vouchers, offers, tags, attribution and a payment method.
Update Order Partially updates an order's status, fulfillment status, tags, addresses, attribution or metadata. Only the fields you supply change. The vendor also publishes a PUT on this route with an identical body, so it is not shipped separately: this operation covers both.
Cancel Order Cancels an order with a reason, optionally refunding it in full and optionally emailing the customer. This is not reversible and Full Refund moves real money: run Calculate Order Refund first if you want to see the amounts before committing.
Capture Order Payment Captures the full amount previously authorized against the order, turning an authorization into a settled payment. It captures the total, not a partial amount: use Capture Transaction when you need to capture part of an authorization.
Collect Order Payment Charges the order's outstanding balance against the payment method it was placed with. It only works when that gateway supports merchant initiated transactions, so it is the dunning operation for saved cards rather than a general charge route.
Mark Order As Paid Records an order as paid without charging anything, for money collected outside the store such as a bank transfer or cash on delivery.
Calculate Order Refund Calculates what a refund would come to without moving any money, returning the per line amounts, taxes and shipping. Run this before Refund Order: a refund cannot be undone, and this is the only dry run the API offers.
Refund Order Refunds an order against one or more of its transactions, with per line quantities and restock handling and an optional shipping refund.
Add Order Line Items Adds items to an existing order and charges the order's original payment method for them. This takes money. Add Order Line adds a line without charging; use that one when you only want to correct an order.
Add Order Line Adds a single line item to an order without charging for it, with an optional custom price and a reason recorded in the order history.
Update Order Line Changes the quantity, properties or metadata of a line on an existing order, with a reason recorded in the order history. It does not adjust what has already been charged; use Refund Order or Add Order Line Items for the money side.
Delete Order Line Removes a line item from an order. This changes the order's contents but does not refund anything that was already charged for that line, so pair it with Refund Order when money has moved.
List Order Notes Lists the internal notes recorded against an order, newest first. These are staff notes and are never shown to the customer.
Create Order Note Records an internal note against an order. This is the natural place for a flow to leave its audit trail, since the note appears alongside the order in the dashboard where a human will look for it.
List Order Fulfillments Lists the fulfillments (shipments) created against an order, each with its carrier, tracking code and line items.
Create Order Fulfillment Marks specific order lines as shipped with a carrier and tracking code, optionally emailing the customer. Leave Lines empty and the whole order is fulfilled; that is easy to do accidentally on a split shipment.
Get Order Fulfillment Returns a single fulfillment on an order with its carrier, tracking details, line items and current delivery status.
List Fulfillment Events Lists the tracking events recorded against a fulfillment, which is the delivery timeline the customer sees on the order status page.
Create Fulfillment Event Adds a delivery tracking event to a fulfillment, with a status, timestamp, location and message. This is how a carrier or a third party tracking service feeds delivery progress into the store, and it is what drives the order's delivery status.
Get Fulfillment Event Returns a single tracking event from a fulfillment's delivery timeline.
Delete Fulfillment Event Removes a tracking event from a fulfillment's delivery timeline. The order's delivery status is recalculated from whatever events remain, so removing the latest one moves the order backwards in the timeline.
List Order Fulfillment Orders Lists the fulfillment orders belonging to an order. A fulfillment order is the work assigned to one location; an order split across two warehouses has two of them, and each is accepted, held or moved independently.

Customers

List Customers Lists the store's customers with filters for email, name, phone number, language, join date, blocked state and marketing consent. Customers are the users resource in this API, and unlike orders they are addressed by numeric id.
Get Customer Returns a customer with their addresses, tags, metadata, lifetime order count and total spent.
Create Customer Creates a customer with their email, name, phone number, language, tags, metadata and any number of addresses. Email is the identity here: creating a second customer with an address already in use is refused rather than merged.
Update Customer Partially updates a customer's email, name, phone number, language, tags, metadata, marketing consent or blocked state. The vendor also publishes a PUT with an identical body, so it is not shipped separately.
List Customer Addresses Lists the addresses stored on a customer's account, including which are their defaults for shipping and billing.
Get Customer Address Returns a single address from a customer's account.
Create Customer Address Adds an address to a customer's account and can set it as their default for shipping or billing. Line 4 is the city in this API, despite its name, and it is required along with Line 1 and Country.
Update Customer Address Replaces an address on a customer's account. The vendor offers only a full replace here, no PATCH, so any field you leave out is cleared: read the address with Get Customer Address first and send it back with your changes applied.
Delete Customer Address Removes an address from a customer's account. Orders already placed keep the address they were shipped to.
List Customer Notes Lists the internal staff notes recorded against a customer.
Create Customer Note Records an internal note against a customer, visible to staff in the dashboard and never to the customer.
List Customer Orders Lists every order a customer has placed. Cheaper and more reliable than filtering List Orders by name or email, because it follows the customer record rather than matching text.
List Customer Subscriptions Lists every subscription belonging to a customer, with its status, interval and next renewal date. The natural first step in a churn save or a payment recovery flow.

Products

List Products Lists catalog products with filters for title, category, product range, SKU, public visibility and gift card status. Each row carries its variants, images and categories.
Get Product Returns a product with its variants, variant attributes, images, prices, categories, subscription settings and metadata.
Create Product Creates a catalog product with its description, categories, subscription settings, SEO fields and, in the same call, its variant attributes and variants with their SKUs, prices and stock records.
Update Product Partially updates a product's title, description, categories, visibility, subscription settings, SEO fields or metadata. Supplying Variants here replaces the variant list, so send only what you mean to keep, or use the variant operations instead.
Delete Product Deletes a product and its variants from the catalog. This is not reversible. Setting Is Public off with Update Product hides a product from the storefront without destroying it, and is usually what you want.
List Product Images Lists the images attached to a product, in display order. The image with display order zero is the product's primary image.
Get Product Image Returns a single product image with its caption, display order and hosted URL.
Create Product Image Attaches an image to a product, either by giving a URL the store fetches or by sending the file inline as base64.
Update Product Image Changes an image's caption, display order or the variants it belongs to. The image file itself cannot be swapped: delete the image and add a new one.
Delete Product Image Removes an image from a product. If it was the primary image, the next image in display order takes its place.
List Product Prices Lists a product's prices, one entry per currency, each with its selling price, compare-at retail price and subscription price.
Get Product Price Returns a product's price in one currency. Prices are addressed by currency code here, not by an id.
Create Product Price Adds a price for a product in a currency, with an optional compare-at retail price, subscription price and cancellation downsell price. A product needs a price in every currency the store or campaign sells in, or checkout in that currency fails.
Update Product Price Changes a product's price in one currency. Existing subscriptions keep the price they were signed up at; changing the subscription price here affects new signups only.
Delete Product Price Removes a product's price in one currency. The product then cannot be bought in that currency, and a campaign that offers it will fail at checkout.
List Product Variants Lists the variants of a parent product, each with its SKU, prices, stock records and attribute values.
Create Product Variant Adds a variant to a parent product with its SKU, prices, opening stock records and attribute values. Variant Attribute Values is required and must name attributes the parent product already declares.
Get Variant Returns a single product variant. Variants have their own top level route, /products/variants/{id}/, and take the variant id rather than the parent product's.
Update Variant Partially updates a variant's SKU, prices, stock tracking, backorder policy, unit cost or attribute values. Supplying Prices replaces the price list for every currency, so include the ones you want to keep.
Delete Variant Deletes a product variant. This is not reversible, and it takes the variant's stock records and prices with it.
List Stock Records Lists inventory records across the store, one per product and fulfillment location, with filters for SKU, location, inventory availability and purchase availability.
Get Stock Record Returns a single stock record, which is one product's inventory at one fulfillment location.
Create Stock Record Creates an inventory record for a product at a fulfillment location, with an opening quantity and a low stock threshold. A product with no stock record at a location cannot be fulfilled from it.
Update Stock Record Sets a stock record's quantity on hand or its low stock threshold. Quantity In Stock is an absolute value, not a delta: sending 5 sets the level to five rather than adding five, so read the record first if you mean to adjust it.
Delete Stock Record Removes a product's inventory record at a fulfillment location. The product can then no longer be fulfilled from that location.
List Categories Lists the store's catalog categories with their slugs, images, templates and public visibility.
Get Category Returns a single catalog category with its description, image, SEO fields and template.
Create Category Creates a catalog category with a name, URL slug, description, image, SEO fields and an optional custom theme template.
Update Category Replaces a catalog category. The vendor offers only a full replace here, no PATCH, so Name and Slug are required and anything you leave out is cleared: read the category with Get Category first and send it back with your changes applied.

Subscriptions

List Subscriptions Lists subscriptions with filters for status, renewal and cancellation dates, product or SKU, gateway and card brand, customer email or phone, payment method, recovery source and the full attribution set.
Get Subscription Returns a subscription with its lines, customer, addresses, payment details, interval, next renewal date and the orders it has generated.
Create Subscription Creates a subscription for a customer with its lines, billing interval, first renewal date, addresses and payment details. Payment Method here accepts only Card Token: a subscription needs a stored card the store can bill again without the customer present.
Update Subscription Changes a subscription's interval, next renewal date, status, addresses, shipping or payment details. Paused is not writable here: use Pause Subscription and Resume Subscription, which handle the pause window and the auto cancellation that follows it.
Cancel Subscription Cancels a subscription with a structured reason, optionally emailing the customer. This is not reversible: a canceled subscription is not resumed, it is replaced by a new one.
Pause Subscription Pauses a subscription, either until a given date or indefinitely. An indefinite pause is not permanent: the vendor auto cancels a subscription that has not been resumed within six months, so a pause with no Pause Until date is a six month clock, not a hold.
Resume Subscription Reactivates a paused subscription and sets when its next renewal falls due. Next Renewal Date is required and must be in the future; there is no way to resume and bill immediately from this route.
Renew Subscription Triggers a renewal order immediately rather than waiting for the schedule. This charges the customer now and creates a real order, so it is not a way to test a subscription.
Retry Subscription Payment Retries the payment for a past due or retrying subscription, optionally through a different gateway. Pointing the retry at a second gateway is the standard recovery play when the original one is declining.
Add Subscription Line Adds a product to what a subscription bills on each cycle, with an optional custom price. It changes future renewals only; nothing is charged now.
Update Subscription Line Replaces a line on a subscription. The vendor offers only a full replace here, no PATCH, so Quantity is required and any price, properties or metadata you leave out are cleared.
Delete Subscription Line Removes a line from a subscription so it is no longer billed on future cycles. Orders already generated are untouched.
List Subscription Transactions Lists the payment attempts made against a subscription, successful and failed. The failure reasons here are what a recovery flow branches on.

Fulfillment

List Fulfillment Orders Lists fulfillment orders across the store with filters for order number, location, status, request status, shipping method, product and SKU. A fulfillment order is the work assigned to one location, so an order split across two warehouses appears here twice and each half is progressed independently.
Get Fulfillment Order Returns a fulfillment order with its line items, assigned location, status, request status and any hold reason.
List Assigned Fulfillment Orders Lists the fulfillment orders assigned to a fulfillment service, filtered by location, assignment status and creation date. This is the fulfillment partner's own inbox: it needs the fulfillment_service scope rather than the merchant's fulfillment_orders scope.
Get Fulfillment Order Locations Lists the fulfillment locations that can take a given fulfillment order, based on stock and shipping coverage. Call this before Move Fulfillment Order: moving work to a location that cannot ship it is refused, and this is how you find one that can.
Cancel Fulfillment Order Cancels a fulfillment order outright, as the merchant. This is the merchant's own cancellation. Send Cancellation Request is the different, negotiated route used when a fulfillment service has already accepted the work.
Close Fulfillment Order Marks a processing fulfillment order as incomplete and closes it, for work that will never be finished, with a message explaining why.
Hold Fulfillment Order Puts a fulfillment order on hold with a structured reason so the warehouse does not pick it. The natural response to a fraud check, an address problem or an unpaid balance, and it is reversible with Release Fulfillment Order Hold.
Release Fulfillment Order Hold Takes a fulfillment order off hold so it can be picked and shipped again.
Move Fulfillment Order Reassigns a fulfillment order, or specific line items from it, to another fulfillment location. Moving only some line items splits the fulfillment order in two.
Send Fulfillment Request Asks the fulfillment service assigned to a fulfillment order to fulfill it, optionally for specific line items only. This is the merchant's half of the handshake; the service then answers with Accept Fulfillment Request or Reject Fulfillment Request.
Accept Fulfillment Request Accepts a fulfillment request as the fulfillment service, taking responsibility for shipping the work. This is the fulfillment service's side of the handshake and needs the fulfillment_service scope, not the merchant's.
Reject Fulfillment Request Rejects a fulfillment request as the fulfillment service, with a structured reason such as out of stock or an undeliverable address. The reason is what lets the merchant's flow react automatically rather than waiting for a human to read a message.
Cancel Fulfillment Request Withdraws a fulfillment request that has been sent but not yet accepted, returning the work to unrequested. Once the service has accepted it, use Send Cancellation Request instead.
Send Cancellation Request Asks a fulfillment service that has already accepted work to cancel it. This is a request, not a cancellation: the service still answers with Accept Cancellation Request or Reject Cancellation Request, and until then the parcel can still ship.
Accept Cancellation Request Accepts a cancellation request as the fulfillment service, confirming the work will not ship.
Reject Cancellation Request Rejects a cancellation request as the fulfillment service, usually because the parcel has already left. The work stays accepted and will still be shipped, so a merchant flow should fall back to a return rather than assume the cancellation held.
Cancel Cancellation Request Withdraws a cancellation request the merchant sent, letting the fulfillment service carry on with the work.
List Fulfillment Order Fulfillments Lists the shipments created against a fulfillment order, each with its tracking details and line items.
Create Fulfillment Order Fulfillment Records a shipment against a fulfillment order, with tracking information for one or more parcels and the line items each covers. Notify defaults on at the vendor, so leaving it unset emails the customer.
List Locations Lists the store's fulfillment locations with their addresses, allowed destination countries, return policy and callback URLs.
Get Location Returns a single fulfillment location with its address, shipping coverage and callback URL.
Create Location Creates a fulfillment location with its address, the countries it can ship to, whether it accepts returns and a callback URL the store notifies when work is assigned to it.
Update Location Replaces a fulfillment location. The vendor offers only a full replace here, no PATCH, so Address is required and anything you leave out is cleared, the callback URL included.
Delete Location Deletes a fulfillment location. Its stock records go with it, so any product held only there becomes unfulfillable.
List Shipping Methods Lists the store's configured shipping methods with their codes, prices, delivery times and the countries they cover. The code from here is what Create Order and Create Subscription take as Shipping Code.
Get Shipping Method Returns a single shipping method with its price per currency, delivery time and country coverage.

Payments

List Transactions Lists payment transactions with filters for type, status, gateway, card brand and last four, amount range, currency, auth code, network transaction id, 3ds flags and the attribution set.
Get Transaction Returns a single transaction with its gateway response, card details, auth code and the order or subscription it belongs to.
Verify Card Token Checks a card token against a gateway without charging for goods, confirming the card is live and usable. Most acquirers place a small authorization to do this, so it is not entirely invisible on the cardholder's statement.
Capture Transaction Captures funds from a previous authorization, in full or in part. The amount must be between 0.01 and the authorized amount; leaving it empty captures the whole authorization.
Refund Transaction Refunds a specific transaction by amount. This moves real money and cannot be undone, and unlike Refund Order it does not adjust the order's lines or restock anything.
List Gateways Lists the store's payment gateways with their type, active state, supported currencies and card brands, 3ds settings and auto capture behavior. Reading active here explains renewals that silently stop working after a gateway is switched off.
Get Gateway Returns a single payment gateway with its configuration, supported currencies and card brands and its 3ds and capture settings.
List Gateway Groups Lists the store's payment gateway groups with their available currencies and payment methods. A group is what a campaign points at so the store can pick or cascade between gateways at checkout.
Get Gateway Group Returns a single payment gateway group with the currencies, payment methods and card brands it can accept.
List Disputes Lists chargebacks and alerts with filters for type, status, resolution, order number, transaction id, case number, auth code, card details, gateway and dispute date.
Get Dispute Returns a single chargeback or alert with its amount, case number, transaction and current resolution.
Create Dispute Records a chargeback or alert against a transaction, with its amount, case number, ARN and when it happened. This is how an alert feed from a third party service such as Ethoca or Verifi is brought into the store so a flow can refund before the chargeback lands.
Update Dispute Partially updates a dispute's amount, case number, ARN, linked transaction, resolution or metadata. It records a resolution without issuing anything; Resolve Dispute is the route that can also refund.
Resolve Dispute Closes a dispute with a resolution and can create an external refund record at the same time. Create External Refund records money returned outside the gateway; it does not ask the gateway to refund anything.
Delete Dispute Removes a dispute record from the store. This deletes the store's record of the chargeback; it has no effect on the acquirer's case.
List Dispute Notes Lists the internal notes recorded against a dispute, which is where the evidence trail for a representment is usually kept.
Create Dispute Note Records an internal note against a dispute. A flow that gathers delivery evidence should write it here, where the person building the representment will look for it.

Carts

List Carts Lists open and abandoned carts with filters for product, currency, funnel, creation date and the full attribution set. Filtering on Abandoned is the recovery list, and each cart carries the customer's email when they reached that step.
Get Cart Returns a single cart with its lines, customer, vouchers, attribution and totals.
Create Cart Creates an open cart with lines, a customer and attribution, which can then be handed to a checkout to complete. This is the Admin API cart.
Update Cart Replaces a cart's lines, vouchers, attribution and metadata. The vendor offers only a full replace here, no PATCH, so Lines is required and anything you leave out is cleared: read the cart with Get Cart first and send it back with your changes applied.
Delete Cart Deletes an open cart. It disappears from the abandoned cart list too, so deleting carts is also deleting recovery opportunities.

Campaigns

List Campaigns Lists the store's campaigns with filters for name, currency, language and creation or update date. A campaign is a self contained checkout configuration: its own currency, payment gateway group, shipping countries and package catalog.
Get Campaign Returns a campaign's settings: its currencies, language, payment gateway group, enabled payment methods, shipping countries and statement descriptor.
Create Campaign Creates a campaign with its default currency, language, payment gateway group, enabled payment methods, shipping countries and card statement descriptor. The payment methods you may enable are drawn from the gateway group, so pick the group first.
Update Campaign Partially updates a campaign's name, language, currencies, gateway group, payment methods or shipping countries. The array fields replace their lists rather than adding to them.
Delete Campaign Deletes a campaign and its packages. Any live checkout page pointing at this campaign stops working immediately, and its Campaigns API key stops authenticating.
List Campaign Packages Lists the packages a campaign offers, filtered by package name, product name or SKU. A package is what a checkout page actually sells: a product or variant bundled with a quantity, a price and optional subscription terms.
Get Campaign Package Returns a single campaign package with its product, variants, prices and subscription terms.
Create Campaign Package Adds a package to a campaign, linking a product and optionally specific variants, with a unit price and optional recurring subscription terms.
Update Campaign Package Changes a campaign package's name, product, variant, prices or subscription terms. Recalculate Prices fills in the currencies you did not list from the campaign's default currency price, which is how a multi currency campaign is repriced in one call.
Delete Campaign Package Removes a package from a campaign. Any checkout page referencing that package id stops working, and existing subscriptions created from it are unaffected.

Gift Cards

List Gift Cards Lists gift cards with filters for code, name or email, customer, status, currency, amount range and issue date.
Get Gift Card Returns a single gift card with its code, remaining balance, currency, expiry and the customer it belongs to.
Create Gift Card Issues a gift card for an amount in a currency, optionally assigned to a customer and with an expiry date. The card can only be spent in the currency it was issued in, and the store generates the code.
Update Gift Card Changes a gift card's expiry date or the customer it belongs to. The balance cannot be topped up through this route: issue a second card instead.
Deactivate Gift Card Disables a gift card so its remaining balance can no longer be spent. The balance is not refunded anywhere: it simply stops being usable.

Exports

List Exports Lists the CSV exports requested from the store, with their type, date range and current state.
Get Export Returns a single export with its type, date range and current state. Poll this after Create Export until the export reports complete, then call Get Export Download URL.
Create Export Asks the store to build a CSV export of one data type over a date range. The export is built asynchronously: this returns straight away with an id, and the file is not ready until Get Export reports it complete.
Get Export Download URL Returns the download URL for a completed export file. It only answers once the export has finished building, and the URL is time limited, so fetch the file promptly rather than storing the link.
List Export Types Returns the export types this store actually supports, as codes with display names. This is the store's own live list and is the authority if the fixed dropdown on Create Export ever drifts from it.

Support

List Tickets Lists support tickets with filters for free text, subject, status, priority, channel, requester, assignee, order number, product, tags, ticket type and creation date.
Get Ticket Returns a single support ticket with its subject, status, priority, requester, assignee and linked order and products.
Create Ticket Opens a support ticket, optionally linked to a customer, an order and products, with a first comment. A ticket created here is recorded with the API channel, so it is easy to tell apart from one a human opened.
Update Ticket Partially updates a ticket's status, priority, assignee, tags, linked order or type, and can add a comment in the same call. Tags replaces the tag list.
List Ticket Comments Lists the comments on a support ticket, both the public replies the customer sees and the internal notes they do not.
Create Ticket Comment Adds a comment to a support ticket, with attachments if any have been uploaded. Is Public decides whether the customer sees it: leave it off for an internal note, turn it on to reply to them.
Upload Ticket Attachment Uploads a file for use on a ticket comment and returns its attachment id. This is a two step flow: the upload does not attach the file to anything on its own, so pass the id it returns into Create Ticket Comment as an Attachment ID.
List Ticket Types Lists the store's ticket types, which are its own categorization of support requests.
Get Ticket Type Returns a single ticket type by id.

Storefront

List Pages Lists the store's content pages with their slugs, titles and SEO fields.
Get Page Returns a single storefront page with its full HTML content, slug, template and SEO fields.
Create Page Creates a content page on the storefront with its HTML body, URL slug, SEO fields and an optional custom theme template.
Update Page Partially updates a storefront page's title, content, slug, SEO fields, template or metadata. Changing the slug changes the public URL and breaks any link pointing at the old one.
Delete Page Deletes a storefront page. Its URL starts returning a not found page immediately, so redirect anything pointing at it first.
List Themes Lists the store's storefront themes and shows which one is active.
Get Theme Returns a single storefront theme with its name and whether it is the live one.
Create Theme Creates a storefront theme. Setting Active on publishes it to the live storefront at once, so create it inactive, add its templates, and activate it as a separate step.
Delete Theme Deletes a storefront theme and its templates. This is not reversible and there is no export route to take a copy first, so keep theme source in version control outside the store.
List Theme Templates Lists the template files in a storefront theme.
Create Theme Template Adds or replaces a template file in a theme, either from inline content or from a file URL the store fetches. If the theme is the active one, the change is live on the storefront as soon as this returns.
Delete Theme Templates Removes template files from a theme. The vendor publishes this route with no template identifier and no body, so it addresses the theme's templates collection rather than one named file.

Metadata

List Metadata Definitions Lists the store's custom field definitions with the object they attach to, their data type and whether they are exportable or filterable.
Get Metadata Definition Returns a single custom field definition with its key, object, data type and validation rules.
Create Metadata Definition Defines a custom field on orders, customers, products, variants, line items, disputes, pages, blogs or attribution. This must exist before the key can be written: sending metadata whose key has no definition is rejected, which is the usual cause of a create failing on a field that looks harmless.
Update Metadata Definition Changes a custom field's name, the object it attaches to, its export and filter settings or its validation rules. The key and the data type are not changeable here.
Delete Metadata Definition Removes a custom field definition from the store. Records will stop accepting that key immediately, and a flow that has been writing it starts failing rather than silently dropping the value.

Webhooks

List Webhooks Lists the store's webhook endpoints with their events, target URLs, api_version, active state, warning count and next check date. This is where a trigger that went quiet is diagnosed: the vendor deactivates an endpoint that keeps failing, and active, warning_count and next_check_date say so.
Get Webhook Returns a single webhook endpoint with its events, target, signing secret, api_version, active state and failure counters.
Create Webhook Registers a webhook endpoint for one or more store events. You may supply your own signing secret, which removes the usual read-it-back step and lets a receiver be configured before the webhook exists.
Update Webhook Changes a webhook's target, events, name, secret, api_version or active state. Events replaces the subscription list, so include every event you want to keep.
Delete Webhook Deletes a webhook endpoint. Deliveries stop immediately and nothing is queued for later, so any event that happens after this is simply not delivered.

Checkout

Get Checkout Campaign Returns the campaign the Campaigns API Key belongs to, with its packages, currencies, shipping methods and available payment methods. This is the other API: a global host, a campaign key rather than the store access token, and a 403 rather than a 401 when the credential is missing.
Create Checkout Cart Creates a cart on the Campaigns API from campaign package ids, with the shopper's details and optional vouchers and attribution. Lines take package IDS, not product IDS: a package is the campaign's own sellable unit, and a product id here matches nothing.
Calculate Checkout Cart Prices a set of campaign packages with vouchers and a shipping method applied, without creating anything. This is the totals call a checkout page makes on every change, and it is how a flow checks what an offer code is worth before committing to it.
Create Checkout Order Places an order through the Campaigns API and takes payment, returning the order and, for redirect based methods, the URL to send the shopper to.
Get Checkout Order Returns an order created through the Campaigns API by its reference id. It is addressed by the checkout ref_id, not by the order number the Admin API uses, so the two identifiers are not interchangeable.
Add Checkout Order Upsell Adds packages to an order that has already been paid for and charges the same payment method again, which is the one click post purchase upsell.
Autocomplete Address Suggests addresses from a partial string, for a checkout address field. Using it before Create Checkout Order reduces undeliverable address rejections at the fulfillment stage.

Triggers

1 triggers

Event Triggers

On Store Event Fires when the store reports an order, customer, product, subscription, transaction, fulfillment, dispute, gateway, cart, export, ticket, store or app event. Each delivery is verified against the HMAC-SHA256 signature this connector registers with the webhook, so a forged post never starts a flow.

Frequently Asked Questions

What can FlowRunner do with 29 Next?

FlowRunner agents can run Get Store, List Orders, and Get Order in 29 Next, plus 183 more actions.

Does connecting 29 Next to FlowRunner require OAuth?

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

Can 29 Next trigger a FlowRunner workflow automatically?

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

Start building with 29 Next

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us