What is an organization?
Every Nymble Commerce tenant is an organization with a uniqueOrganizationId. When you authenticate, your JWT carries this identifier automatically — you don’t need to pass it as a query parameter or request body field in most API calls. Nymble Commerce reads it from your token and scopes every read and write to your organization only.
Organizations are useful across several deployment patterns:
- Multi-brand operators — run distinct storefronts under a single Nymble Commerce subscription, each with its own product catalog and customer base.
- Agencies and platforms — manage multiple client accounts from one place, with complete data isolation between clients.
- SaaS platforms with tenant isolation — give each of your customers their own scoped environment without building isolation logic yourself.
OrgCode vs OrganizationId
Nymble Commerce uses two different organization identifiers for different purposes:
You supply the
OrgCode at login time. From that point on, your JWT carries the OrganizationId and Nymble Commerce uses it automatically. You rarely need to reference OrganizationId directly in your integration code.
Data isolation
Every resource in Nymble Commerce is scoped to exactly one organization. The API enforces this at the data layer — not just the application layer — so there is no risk of cross-tenant data leakage. The following resource types are fully isolated per organization:
No API key, user token, or admin credential from one organization can read or write data belonging to another organization.
Organization hierarchy
Your organization acts as the root of a tree that all your commerce data hangs from:Organization settings
You can configure the following at the organization level. Changes apply to all users, customers, and API calls within your org.
For full integration configuration details, see the Integrations guide.