Build on Zopping

Zopping is a multi-tenant e-commerce and retail platform. This portal documents its APIs for partners and providers — syncing catalog, fulfilling orders, powering storefronts, processing payments, and more.

The API is organized by commerce domain — Catalog, Orders, Inventory, Customers, Promotions, Fulfillment, Payments — rather than by internal service.

One Platform API, two gateways

Zopping exposes a single Platform API through two gateways, distinguished by who authenticates:

• Backend gateway — https://zopping.com/api/<service>/<resource>. Staff- and partner-authenticated (employee roles, or a partner Developer-Token). The full surface for managing a store: catalog, pricing, stock, orders, promotions.
• Storefront gateway — https://<store-domain>/api/.... A subset, public and end-customer-authenticated (a shopper session): browse, cart, checkout, account. See Build a storefront.

How the platform fits together

• Organization-scoped — a credential is bound to one organization (the retailer) and only ever sees that tenant's data.
• Store-aware — an organization can run multiple stores. Resources that vary by store (price, stock, slots) take a storeId.
• RBAC-governed — a developer grant determines which methods are permitted on each resource. A documented endpoint is not necessarily callable by a given token until that access is granted.
• Extensible — optional extensions change which features and fields are available per organization.

Where to start

Foundations

Before building, review Core concepts & data model, Authentication, Extensions, Custom fields & metaData, and Responses & errors.