Platform Capabilities

This page and capabilities.json are the same generated projection (2026-09-03) over the two documentation sites and the Admin API specification. Each capability has a stable id that pages on both sites declare in their frontmatter. Links, operations, and events come from the owning sources; when they disagree with this page, the guide, the spec, or the changelog wins.

Agents: fetch a domain bundle rather than this page when you need the prose behind a capability. The JSON schema is at capabilities.schema.json.

Bundles

Capabilities

Admin API

id: admin-api · status: available · audiences: developer · links verified 2026-09-03

The REST Admin API manages store resources: products, orders, customers, subscriptions, fulfillment, payments, campaigns, and more. Access is by OAuth app token against https://{store}.29next.store/api/admin/, with the version selected per request by the X-29next-API-Version header. 2024-04-01 is the stable version; 2023-02-10 is deprecated; unstable carries in-progress changes.

The developer portal has no changelog of its own; version history is on the merchant changelog. There is no consolidated migration guide between API versions yet.

Merchant guides

• docs.nextcommerce.com/docs/build-a-store/technical-settings/configure-webhooks
• docs.nextcommerce.com/changelog

Developer guides

• /docs/admin-api
• /docs/admin-api/permissions
• /docs/admin-api/guides/exports

Admin API operations (12, version 2024-04-01)

• GET /store/ Retrieve general business information and store settings.
• GET /exports/ Retrieve a list of exports.
• POST /exports/ Create a new export.
• GET /exports/types/ Retrieve all available export types.
• GET /exports/{id}/ Retrieve an export.
• GET /exports/{id}/download/ Retrieve the download URL for a completed export file.
• GET /metadata/ Retrieve a list of metadata definitions.
• POST /metadata/ Create a new metadata definition.
• GET /metadata/{id}/ Retrieve a metadata definition.
• PUT /metadata/{id}/ Update an existing metadata definition.
• PATCH /metadata/{id}/ Partial update an existing metadata definition.
• DELETE /metadata/{id}/ Delete an existing metadata definition.

Webhook events (2)

• export.created
• store.updated

AI agent skills

• next-ops-scan

Orders and external checkout

id: orders · status: available · audiences: merchant, developer · links verified 2026-09-03

Orders can be created through the Admin API from an external checkout (cart, order, upsell flow) and managed afterwards: fulfil, refund, capture, cancel, and edit. Campaign and storefront orders land in the same orders list.

Merchant guides

• docs.nextcommerce.com/docs/manage/orders/collect-payments-on-orders
• docs.nextcommerce.com/docs/manage/orders/test-orders

Developer guides

• /docs/admin-api/guides/external-checkout
• /docs/admin-api/guides/order-management

Admin API operations (30, version 2024-04-01)

• GET /orders/ Retrieve a list of orders.
• POST /orders/ Create a new order.
• GET /orders/{number}/ Retrieve a order.
• PUT /orders/{number}/ Update an existing order.
• PATCH /orders/{number}/ Partial update an existing order.
• POST /orders/{number}/add-line-items/ Add additional items to the order and charge the initial order payment method.
• POST /orders/{number}/cancel/ Cancel an existing order.
• POST /orders/{number}/capture/ Captures the total amount of the previously authorized funds for this order.
• POST /orders/{number}/collect-payment/ Collect payment for an order outstanding balance on the order.
• GET /orders/{number}/fulfillment-orders/ Retrieves a list of fulfillment orders for a specific order.
• GET /orders/{number}/fulfillments/ Retrieve order fulfillments.
• POST /orders/{number}/fulfillments/ Add shipment order for separate line.
• GET /orders/{number}/fulfillments/{fulfillmentId}/ Retrieve an existing order fulfillment.
• GET /orders/{number}/fulfillments/{fulfillmentId}/events/ Retrieve a list of fulfillment events of a order fulfillment.
• POST /orders/{number}/fulfillments/{fulfillmentId}/events/ Create a fulfillment event in an existing order fulfillment.
• GET /orders/{number}/fulfillments/{fulfillmentId}/events/{eventId}/ Retrieve a fulfillment event.
• DELETE /orders/{number}/fulfillments/{fulfillmentId}/events/{eventId}/ Delete an existing fulfillment event.
• POST /orders/{number}/lines/ Add a new line item to an existing order.
• PATCH /orders/{number}/lines/{lineId}/ Update an existing line item in an order.
• DELETE /orders/{number}/lines/{lineId}/ Remove a line item from an existing order.
• POST /orders/{number}/mark-as-paid/ Marks an order as paid.
• GET /orders/{number}/notes/ Retrieve a list of all order notes in an existing order.
• POST /orders/{number}/notes/ Create an order note in an existing order.
• POST /orders/{number}/refund/ Refund an existing order.
• POST /orders/{number}/refund/calculate/
• GET /carts/ Retrieve a list of all open carts.
• POST /carts/ Create a new cart.
• GET /carts/{id}/ Retrieve a cart.
• PUT /carts/{id}/ Update an existing cart.
• DELETE /carts/{id}/ Delete an existing cart.

Webhook events (3)

• order.created
• order.updated
• cart.abandoned

Subscriptions

id: subscriptions · status: available · audiences: merchant, developer · links verified 2026-09-03

Native recurring orders. Merchants configure phases, statuses, pause, cancellation paths, decline salvage, and account updater in the dashboard; developers create and manage subscriptions through the Admin API. Renewals are not a separate webhook: a renewal surfaces as transaction.created (and order.created) with billing_cycle set.

There is no subscription.renewed event. Detect renewals from transaction.created with billing_cycle.

Merchant guides

• docs.nextcommerce.com/docs/manage/subscriptions-guide
• docs.nextcommerce.com/docs/manage/subscriptions-guide/managing-subscriptions
• docs.nextcommerce.com/docs/manage/subscriptions-guide/subscription-phases
• docs.nextcommerce.com/docs/manage/subscriptions-guide/subscription-statuses
• docs.nextcommerce.com/docs/manage/subscriptions-guide/subscription-settings
• docs.nextcommerce.com/docs/manage/subscriptions-guide/pause-subscriptions
• docs.nextcommerce.com/docs/manage/subscriptions-guide/cancellation-paths
• docs.nextcommerce.com/docs/manage/subscriptions-guide/decline-salvage
• docs.nextcommerce.com/docs/manage/subscriptions-guide/account-updater
• docs.nextcommerce.com/docs/analytics/subscription-performance

Developer guides

• /docs/admin-api/guides/subscription-management

Admin API operations (13, version 2024-04-01)

• GET /subscriptions/ Retrieve a list of subscriptions.
• POST /subscriptions/ Create a new subscription.
• GET /subscriptions/{id}/ Retrieve a subscription.
• PATCH /subscriptions/{id}/ Partial update an existing subscription.
• POST /subscriptions/{id}/cancel/ Cancel an existing subscription.
• POST /subscriptions/{id}/lines/ Create a new subscription line.
• PUT /subscriptions/{id}/lines/{lineId}/ Update an existing subscription line.
• DELETE /subscriptions/{id}/lines/{lineId}/ Delete a subscription line in an existing subscription line.
• POST /subscriptions/{id}/pause/ Pause an existing subscription.
• POST /subscriptions/{id}/renew/ Trigger a subscription renewal order.
• POST /subscriptions/{id}/resume/ Resume a paused subscription.
• POST /subscriptions/{id}/retry/ Trigger a renewal payment retry for a subscription.
• GET /subscriptions/{id}/transactions/ Retrieve a list of transactions in an existing subscription.

Webhook events (3)

• subscription.created
• subscription.updated
• transaction.created

AI agent skills

• next-bulk-subscription

Payments and gateways

id: payments-gateways · status: available · audiences: merchant, developer · links verified 2026-09-03

Merchants add bankcard gateways and alternative payment methods under Settings > Payments and group them for routing and failure cascading. Developers choose a gateway on an API-created order with payment_details.payment_gateway or payment_gateway_group, and integrate each payment method through its guide. NEXT Payments is the platform's own processing service.

NEXT Payments processing rates are not published in the documentation; they are quoted by sales.

Merchant guides

• docs.nextcommerce.com/docs/features/payments
• docs.nextcommerce.com/docs/start-here/get-started/add-payment-providers
• docs.nextcommerce.com/docs/features/payments/gateways/next-payments
• docs.nextcommerce.com/docs/features/payments/payment-failure-cascading
• docs.nextcommerce.com/docs/features/payments/authorize-and-capture-payments
• docs.nextcommerce.com/docs/features/payments/3ds2-payments
• docs.nextcommerce.com/docs/features/payments/external-payment-methods
• docs.nextcommerce.com/docs/features/payments/risk-screening
• docs.nextcommerce.com/docs/features/payments/transaction-response-codes

Developer guides

• /docs/admin-api/guides/payment-methods
• /docs/admin-api/guides/payment-methods/bankcard
• /docs/admin-api/guides/payment-methods/apple-pay
• /docs/admin-api/guides/payment-methods/google-pay
• /docs/admin-api/guides/payment-methods/paypal
• /docs/admin-api/guides/payment-methods/klarna
• /docs/admin-api/guides/payment-methods/affirm
• /docs/admin-api/guides/payment-methods/afterpay
• /docs/admin-api/guides/payment-methods/link
• /docs/admin-api/guides/payment-methods/bancontact
• /docs/admin-api/guides/payment-methods/ideal
• /docs/admin-api/guides/payment-methods/sepa-debit
• /docs/admin-api/guides/payment-methods/swish
• /docs/admin-api/guides/payment-methods/twint

Admin API operations (18, version 2024-04-01)

• GET /disputes/ Retrieve a list of disputes.
• POST /disputes/ Create a new dispute.
• GET /disputes/{id}/ Retrieve a dispute.
• PUT /disputes/{id}/ Update an existing dispute.
• PATCH /disputes/{id}/ Partial update an existing dispute.
• DELETE /disputes/{id}/ Delete an existing dispute.
• GET /disputes/{id}/notes/ Retrieve a list of all dispute notes in an existing dispute.
• POST /disputes/{id}/notes/ Create an dispute note in an existing dispute.
• POST /disputes/{id}/resolve/ Resolve a dispute with a resolution and optional external refund.
• GET /gateway-groups/ Retrieve a list of gatway groups.
• GET /gateway-groups/{id}/ Retrieve a gatway group.
• GET /gateways/ Retrieve a list of gateways.
• GET /gateways/{id}/ Retrieve a gateway.
• GET /transactions/ Retrieve a list of transactions.
• POST /transactions/verify/ Verify a card token.
• GET /transactions/{id}/ Retrieve a transaction.
• POST /transactions/{id}/capture/ Capture an existing transaction.
• POST /transactions/{id}/refund/ Refund an existing transaction.

Webhook events (4)

• gateway.created
• gateway.updated
• transaction.created
• transaction.updated

Disputes

id: disputes · status: available · audiences: merchant, developer · links verified 2026-09-03

Disputes are chargebacks. Merchants review and respond to them in the dashboard and report on them; apps can act as a dispute service and receive dispute events.

Merchant guides

• docs.nextcommerce.com/docs/features/payments/disputes-guide
• docs.nextcommerce.com/docs/analytics/disputes-reports

Developer guides

• /docs/apps/guides/dispute-service

Webhook events (2)

• dispute.created
• dispute.updated

Fulfillment

id: fulfillment · status: available · audiences: merchant, developer · links verified 2026-09-03

Orders are fulfilled through locations, fulfillment statuses, and location-based routing. Apps can register as a fulfillment service and receive assigned fulfillment orders through the Admin API.

Merchant guides

• docs.nextcommerce.com/docs/features/fulfillment-guide
• docs.nextcommerce.com/docs/features/fulfillment-guide/fulfillment-statuses
• docs.nextcommerce.com/docs/features/fulfillment-guide/location-based-routing
• docs.nextcommerce.com/docs/features/fulfillment-guide/advanced-settings
• docs.nextcommerce.com/docs/start-here/get-started/fulfillment-settings

Developer guides

• /docs/apps/guides/fulfillment-service

Admin API operations (26, version 2024-04-01)

• GET /assigned-fulfillment-orders/ Retrieve assigned fulfillment order requests
• GET /fulfillment-orders/ Retrieve a list of fulfillment orders.
• GET /fulfillment-orders/{id}/ Retrieve a fulfillment order.
• GET /fulfillment-orders/{id}/available-locations/ Retrieve available locations for a Fulfillment Order.
• POST /fulfillment-orders/{id}/cancel/ Cancel fulfillment order
• POST /fulfillment-orders/{id}/cancellation-request/ Sends a fulfillment cancellation request to the fulfillment service.
• POST /fulfillment-orders/{id}/cancellation-request/accept/ Accepts a fulfillment cancellation request sent to a fulfillment service for a fulfillment order.
• POST /fulfillment-orders/{id}/cancellation-request/cancel/ Cancel a requested fulfillment cancellation request.
• POST /fulfillment-orders/{id}/cancellation-request/reject/ Rejects a fulfillment cancellation request sent to a fulfillment service for a fulfillment order.
• POST /fulfillment-orders/{id}/close/ Marks an processing fulfillment order as incomplete
• POST /fulfillment-orders/{id}/fulfillment-request/ Sends a fulfillment request to the fulfillment service of a fulfillment order.
• POST /fulfillment-orders/{id}/fulfillment-request/accept/ Accepts a fulfillment request sent to a fulfillment service for a fulfillment order.
• POST /fulfillment-orders/{id}/fulfillment-request/cancel/ Cancel Requested Fulfillment Order.
• POST /fulfillment-orders/{id}/fulfillment-request/reject/ Rejects a fulfillment request sent to a fulfillment service for a fulfillment order.
• GET /fulfillment-orders/{id}/fulfillments/ Retrieve Fulfillments for a Fulfillment Order.
• POST /fulfillment-orders/{id}/fulfillments/ Create Fulfillments for a Fulfillment Order.
• POST /fulfillment-orders/{id}/hold/ Hold Fulfillment.
• POST /fulfillment-orders/{id}/move/ Move location of a fulfillment order.
• POST /fulfillment-orders/{id}/release-hold/ Release On Hold Fulfillment.
• GET /locations/ Retrieve a list of all configured fulfillment locations.
• POST /locations/ Create a new fulfillment location.
• GET /locations/{id}/ Retrieve an existing fulfillment location.
• PUT /locations/{id}/ Update an existing fulfillment location.
• DELETE /locations/{id}/
• GET /shipping-methods/ Retrieve a list of all configured shipping methods.
• GET /shipping-methods/{id}/ Retrieve an existing shipping method.

Webhook events (2)

• fulfillment.created
• fulfillment.updated

AI agent skills

• next-bulk-fulfill
• next-bulk-move

Campaigns

id: campaigns · status: available · audiences: merchant, developer · links verified 2026-09-03

Campaigns are custom checkout funnels (landing, checkout, upsell, receipt pages) backed by the CORS-enabled Campaigns API, built with the Campaign Page Kit and starter templates. A campaign's checkout is separate from the storefront checkout, but its orders are ordinary store orders that share the orders list, inventory, and subscriptions.

Merchant guides

• docs.nextcommerce.com/docs/apps/campaigns-app
• docs.nextcommerce.com/docs/apps/campaigns-app/build-campaign-packages
• docs.nextcommerce.com/docs/apps/campaigns-app/campaigns-offers-and-discounts
• docs.nextcommerce.com/docs/apps/campaigns-app/campaign-analytics

Developer guides

• /docs/campaigns
• /docs/campaigns/page-kit
• /docs/campaigns/templates
• /docs/campaigns/api
• /docs/campaigns/admin-api

Admin API operations (20, version 2024-04-01)

• GET /campaigns/ List every campaign belonging to the store.
• POST /campaigns/ Create a campaign's settings.
• GET /campaigns/{id}/ Retrieve a campaign's settings.
• PATCH /campaigns/{id}/ Partial update a campaign's settings.
• DELETE /campaigns/{id}/ Delete a campaign's settings.
• GET /campaigns/{id}/offers/ List every offer on the campaign.
• POST /campaigns/{id}/offers/ Create an offer on the campaign, with its condition and benefit.
• GET /campaigns/{id}/offers/{offerId}/ Retrieve an offer on the campaign.
• PATCH /campaigns/{id}/offers/{offerId}/ Partially update an offer on the campaign.
• DELETE /campaigns/{id}/offers/{offerId}/ Delete an offer on the campaign.
• GET /campaigns/{id}/packages/ List every packages on the campaign.
• POST /campaigns/{id}/packages/ Create a package on the campaign.
• GET /campaigns/{id}/packages/{packageId}/ Retrieve a package on the campaign.
• PATCH /campaigns/{id}/packages/{packageId}/ Partially update a package on the campaign.
• DELETE /campaigns/{id}/packages/{packageId}/ Delete a package on the campaign.
• GET /campaigns/{id}/shipping-methods/ List every shipping method on the campaign.
• POST /campaigns/{id}/shipping-methods/ Create a shipping method on the campaign.
• GET /campaigns/{id}/shipping-methods/{shippingMethodId}/ Retrieve a shipping method on the campaign.
• PATCH /campaigns/{id}/shipping-methods/{shippingMethodId}/ Partially update a shipping method on the campaign.
• DELETE /campaigns/{id}/shipping-methods/{shippingMethodId}/ Delete a shipping method on the campaign.

AI agent skills

• next-campaigns-setup

Storefront themes

id: storefront-themes · status: available · audiences: merchant, developer · links verified 2026-09-03

The hosted storefront is rendered from a theme built with Django Template Language. Merchants install and customise themes under Storefront > Themes; developers build themes locally with Theme Kit (the ntk CLI: ntk pull, ntk push, ntk watch), starting from the Spark starter theme, and query storefront data through the GraphQL API.

Merchant guides

• docs.nextcommerce.com/docs/build-a-store/storefront
• docs.nextcommerce.com/docs/build-a-store/storefront/themes
• docs.nextcommerce.com/docs/build-a-store/storefront/pages-and-assets

Developer guides

• /docs/storefront
• /docs/storefront/themes
• /docs/storefront/themes/theme-kit
• /docs/storefront/themes/settings
• /docs/storefront/themes/translations
• /docs/storefront/themes/cdn-and-caching
• /docs/storefront/themes/templates
• /docs/storefront/themes/templates/objects
• /docs/storefront/themes/templates/tags
• /docs/storefront/themes/templates/filters
• /docs/storefront/themes/templates/urls-and-template-paths
• /docs/storefront/themes/guides/custom-page-templates
• /docs/storefront/themes/guides/custom-product-templates
• /docs/storefront/themes/guides/product-variants
• /docs/storefront/themes/guides/product-metadata
• /docs/storefront/themes/guides/personalized-products
• /docs/storefront/graphql
• /docs/storefront/event-tracking

Admin API operations (13, version 2024-04-01)

• GET /pages/ Retrieve a list of pages.
• POST /pages/ Create a new page.
• GET /pages/{id}/ Retrieve a page.
• PUT /pages/{id}/ Update an existing page.
• PATCH /pages/{id}/ Partially update an existing page.
• DELETE /pages/{id}/ Delete an existing page.
• GET /themes/ Retrieve a list of themes.
• POST /themes/ Create a new theme.
• GET /themes/{id}/ Retrieve a theme.
• DELETE /themes/{id}/ Delete an existing theme.
• GET /themes/{id}/templates/ Retrieve a list of templates in an existing theme.
• POST /themes/{id}/templates/ Create a new template in an existing theme.
• DELETE /themes/{id}/templates/ Delete an existing template in an existing theme.

AI agent skills

• next-theme-dev
• next-theme-figma

Checkout links

id: checkout-links · status: available · audiences: merchant, developer · links verified 2026-09-03

Prebuilt URLs that open the storefront checkout with products, quantities, and attribution already applied, for use from ads, emails, and campaign pages.

Merchant guides

• docs.nextcommerce.com/docs/features/offers/shareable-coupon-links

Developer guides

• /docs/storefront/checkout-links

Apps and OAuth

id: apps · status: available · audiences: developer · links verified 2026-09-03

Apps extend a store through OAuth, a manifest, settings, snippets, and storefront extensions, and can act as fulfillment, dispute, or marketing-attribution services. Merchants install apps from the dashboard; App Kit is the developer toolchain.

The merchant site documents individual apps (Klaviyo, ShipStation, Gorgias, and others) under /docs/apps/<app>, not app installation in general.

Developer guides

• /docs/apps
• /docs/apps/app-development-flow
• /docs/apps/app-kit
• /docs/apps/manifest
• /docs/apps/settings
• /docs/apps/snippets
• /docs/apps/assets
• /docs/apps/review
• /docs/apps/event-tracking
• /docs/apps/oauth
• /docs/apps/oauth/getting-started
• /docs/apps/oauth/install-flows
• /docs/apps/oauth/session-auth
• /docs/apps/guides/server-to-server-apps
• /docs/apps/guides/storefront-extension
• /docs/apps/guides/marketing-attribution

Admin API operations (5, version 2024-04-01)

• GET /apps/{clientId}/ Retrieve a object of app.
• GET /apps/{clientId}/settings/ Retrieve a object of all app settings.
• PUT /apps/{clientId}/settings/ Update an existing app settings.
• PATCH /apps/{clientId}/settings/ Partially update an existing app settings.
• DELETE /apps/{clientId}/settings/ Delete an existing app settings.

Webhook events (1)

• app.uninstalled

Webhooks

id: webhooks · status: available · audiences: merchant, developer · links verified 2026-09-03

Stores send signed JSON webhooks for events on orders, customers, subscriptions, transactions, disputes, fulfillment, products, gateways, tickets, exports, apps, and the store itself. Merchants configure endpoints in the dashboard; developers manage them through the Admin API and verify the X-29Next-Signature header.

Merchant guides

• docs.nextcommerce.com/docs/build-a-store/technical-settings/configure-webhooks

Developer guides

• /docs/webhooks

Admin API operations (6, version 2024-04-01)

• GET /webhooks/ Retrieve a list of webhooks.
• POST /webhooks/ Create a new webhook.
• GET /webhooks/{id}/ Retrieve a webhook.
• PUT /webhooks/{id}/ Update an existing webhook.
• PATCH /webhooks/{id}/ Partial update an existing webhook.
• DELETE /webhooks/{id}/ Delete an existing webhook.

Webhook events (24)

• app.uninstalled
• cart.abandoned
• customer.created
• customer.redacted
• customer.updated
• dispute.created
• dispute.updated
• export.created
• fulfillment.created
• fulfillment.updated
• gateway.created
• gateway.updated
• order.created
• order.updated
• product.created
• product.deleted
• product.updated
• store.updated
• subscription.created
• subscription.updated
• ticket.created
• ticket.updated
• transaction.created
• transaction.updated

Testing and test orders

id: testing · status: available · audiences: merchant, developer · links verified 2026-09-03

There is no separate sandbox. Test cards (6011111111111117, and 6011000990139424 for 3DS) create tagged Test Orders on live stores without touching a gateway; the Test Gateway produces realistic test transactions when an integration needs them.

Do not tell a prospect there is no test mode; test cards work on live stores.

Merchant guides

• docs.nextcommerce.com/docs/manage/orders/test-orders
• docs.nextcommerce.com/docs/features/payments/gateways/test-gateway

Developer guides

• /docs/testing
• /docs/admin-api/guides/testing-guide

Legacy identifiers (29next)

id: legacy-identifiers · status: available · audiences: merchant, developer · links verified 2026-09-03

Next Commerce was formerly 29 Next, and the platform still carries that name in its core technical identifiers: store and account hostnames ({store}.29next.store, accounts.29next.com), the X-29next-API-Version and X-29Next-Signature headers, and the API key namespace. These are current, in use on every store, and not scheduled to change. Use them exactly as written.

Never rewrite 29next identifiers to nextcommerce; the requests would fail.

Merchant guides

• docs.nextcommerce.com/docs/start-here/get-started

Developer guides

• /docs/admin-api
• /docs/webhooks

AI agent skills

id: agent-skills · status: available · audiences: developer · links verified 2026-09-03

Pre-built skills that give AI coding agents platform knowledge (theme development, campaign setup, bulk operations, daily ops scans), installable with the skills CLI or loadable as plain markdown.

Developer guides

• /docs/skills

AI agent skills

• next-theme-figma
• next-theme-dev
• next-campaigns-setup
• next-bulk-fulfill
• next-bulk-move
• next-bulk-subscription
• next-ops-scan