- Shopper Login (SLAS): guest and registered token flows, refresh, logout, password reset and the SLAS admin client/tenant routes (19 routes)
- Baskets and orders: create and modify baskets, items, coupons, shipments, payment instruments and addresses; create and read orders (38 routes)
- Customers: registration, profile, addresses, payment instruments, product lists and order history (25 routes)
- Catalogue and merchandising: products and categories, product search and suggestions, promotions, Page Designer experience, shopper context
- 98 routes (31 read-only) on {shortCode}.api.commercecloud.salesforce.com plus legacy Sites-{site} controllers, documented in the AI integration guide (llms.txt)
Salesforce Commerce Cloud B2C API Connector
Salesforce Commerce Cloud B2C (SFCC) Commerce APIs — SLAS shopper login and admin, Shopper Baskets, Orders, Customers, Products, Search, Promotions, Experience and Context, plus three legacy OCAPI/controller routes — registered in Apivom Atlas as 98 routes on your short-code host at commercecloud.salesforce.com.
What you can do
Use cases
- Orders and customers into the CRM or ERP — Read new orders and customer profiles after checkout and create or update the matching records in the systems your teams work in.
- Headless or composable storefront — Drive baskets, checkout and customer accounts from your own front end using SLAS tokens and the Shopper APIs.
- Catalogue and promotion checks — Query products, prices and active promotions from service tools so support staff answer from live storefront data.
Commerce Cloud B2C — the former Demandware platform — exposes its headless storefront through the Salesforce Commerce API: the Shopper Login and API Access Service (SLAS) issues shopper tokens for guests and registered customers, and the Shopper APIs cover the full purchase path — product search and detail, baskets with items, coupons, shipments and payment instruments, order creation and lookup, customer registration and account data, promotions and Page Designer content — all on a host named by your instance's short code and organisation id. Apivom Atlas registers 98 of these routes, 31 read-only, alongside three legacy OCAPI-era site controllers kept for older storefronts. The credential contract is a SLAS or Account Manager API client; the caller obtains the JWT and Atlas forwards each call to your short-code host. No Apivom product workflow uses Commerce Cloud B2C today — no Apivom product reads baskets, orders or customers from an SFCC instance — so the connector is catalogued for retailers running SFCC who want an Apivom product scoped against their storefront data.
A SLAS or Account Manager API client (client id + secret) for your B2C instance and its short code; the caller obtains the shopper or admin JWT and sends it as Bearer, the short code becomes the per-request base URL on commercecloud.salesforce.com. Apivom Atlas forwards, logs and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Is this Salesforce B2B Commerce?
No. This is Commerce Cloud B2C (SFCC), the standalone platform on commercecloud.salesforce.com with SLAS and Shopper APIs. B2B and D2C Commerce run on the Salesforce core platform and have their own connector in this catalogue.
What identifies my instance?
The short code and organisation id from Business Manager, a site id per storefront, and a SLAS client (public or private) or an Account Manager API client for admin routes. Those values are the credential contract the connector expects.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.