Storefront GraphQL API

The storefront API is a single GraphQL endpoint covering products, carts, orders, collections, customers, content, media, discounts, and more — everything a store needs, one store at a time. Both official SDKs are thin typed wrappers over this schema; call it directly if you need a shape the SDK doesn't expose yet.

Every field that touches store data requires auth (marked @auth in the schema below). Send either a store-scoped public token (read-mostly, safe client-side) or an OAuth app access token (full read/write) as a Bearer token — see Authentication. Fields tagged @auth(roles: ["ADMIN"])additionally require the caller's role to match.

Two custom scalars run through the whole schema: UUID and JSON (freeform metadata blobs). List endpoints that can grow large take a PaginationInput and return a PageInfo:

input PaginationInput {  page: Int  limit: Int} type PageInfo {  total: Int!  hasNextPage: Boolean!  totalPages: Int!}

Products own variants, options/option-values, media, and collection membership. ProductListResponse and InventoryListResponse both page through PageInfo.

query {  listProducts(status: ACTIVE, pagination: { page: 1, limit: 20 }) {    data { id title sellingPrice stock variants { id title stock } }    pageInfo { total hasNextPage }  }}

One cart per authenticated customer — cart always resolves the caller's own cart, there is no cart id argument. Requires a customer session, not a store-level token.

Collections nest via parentId / subCollections and hold products as a many-to-many relationship.

createOrder both places the order and opens a gateway checkout in one call — the response carries a Checkout alongside the order, with everything the browser needs to open the merchant's payment widget. None of it is a secret; the merchant's gateway key never leaves the platform.

Once the browser has run the gateway widget, hand its callback to confirmOrderPayment— the server re-verifies the signature against the merchant's own secret before an order is ever marked paid; nothing from the browser is trusted directly. Not every gateway's browser SDK hands back a signed callback to confirm, though — Cashfree's doesn't. For those, use syncOrderPayment instead: it settles the order by asking the gateway directly for its status, with no client-supplied fields at all.

Customer auth is passwordless email + code, mirroring the account OTP flow but scoped to a store's customers rather than store owners.

The public storefront-facing subset of a store's config — branding, contact info, and CORS settings for embedding the API in a browser app.

Two lightweight CMS types, each independently paginated.

File uploads use the Upload scalar (multipart), organized into nestable folders per store.

Percentage or fixed-amount codes with optional min/max purchase gates, usage limits (total and per-customer), and a date window.

Subscribe/unsubscribe are public — no token required.

Contact form submission is public; reading/managing messages is not.

Named, ordered navigation menus (LinkSet) made of Link nodes that can nest under aparentLinkId and point at a URL or an internal page.

A product listing query, called with a store public token:

curl https://apis.storentia.com/storefront/graphql \  -H "Authorization: Bearer spk_live_9f8e7d6c5b4a3928" \  -H "Content-Type: application/json" \  -d '{    "query": "query { listProducts(status: ACTIVE, pagination: { page: 1, limit: 5 }) { data { id title sellingPrice } pageInfo { total } } }"  }'