ReAI test store · Checkout payments work; test the full flow
ReAI/ commerce
NO
PUBLIC STOREFRONT DATA

Try the Site API with the store’s own data.

All twelve operations in the Site delivery contract: nine reads to try here, checkout through the cart, newsletter signup and back-in-stock notifications. The Site credential stays on the Worker.

Product/collection: handle. Availability: variant ID from a product response; separate batch IDs with commas. Other requests need no value.

Choose a request and try it.

The complete delivery contract

RequestWhat does it show?
GET /site/v1/siteIdentity, markets and locales ↗
GET /site/v1/commerce/storefrontCoherent snapshot for storefront pages ↗
GET /site/v1/commerce/catalogPublished catalog and prices ↗
GET /site/v1/commerce/productsPublished product list ↗
GET /site/v1/commerce/products/{handle}Details, images, variants and optional bundles ↗
GET /site/v1/commerce/collectionsPublished collections ↗
GET /site/v1/commerce/collections/{handle}Ordered membership of one collection ↗
GET /site/v1/commerce/availability/{variantId}Coarse availability for one variant ↗
GET /site/v1/commerce/availabilityCoarse availability for up to 100 variants ↗
POST /site/v1/commerce/stock-subscriptionsOne stock notification with separate consent and a configured flow ↗
POST /site/v1/newsletter/subscriptionsEmail signup with explicit consent ↗
POST /site/v1/commerce/checkout-sessionsStart through the cart; not a read operation ↗

Discounts, shipping selection and payment status are handled in hosted checkout. Rule configuration uses the separate management API; private bank/accounting data is outside this playground.

Delivery OpenAPI ↗

Cart

Product subtotal—

Live catalog from ReAI. Payment mode and recipient are shown before checkout.

View cart