- Catalogue: product search and product detail for a webstore, honouring the buyer's entitlement and price book
- Cart to order: create carts and cart items, open a checkout, update it, tokenise payment, post payments and convert the checkout to an order (9 routes)
- Accounts and orders: buyer account addresses (list/create/update) and order summaries for the storefront account
- Platform access: SOQL query endpoint and the SOAP partner API for records the Commerce routes do not expose
- 17 routes (5 read-only) under /services/data/v{apiVersion}/commerce/webstores/{webstoreId}, documented in the AI integration guide (llms.txt)
Salesforce Commerce B2B/D2C API Connector
Salesforce B2B and D2C Commerce Connect REST APIs on the core platform — webstore product search and product detail, carts and cart items, checkouts, payment tokens and payments, orders and order summaries, buyer account addresses — plus SOQL query and the SOAP partner endpoint, registered in Apivom Atlas as 17 routes on your My Domain org.
What you can do
Use cases
- Punch-out or headless ordering — Build carts and checkouts from a procurement portal or a custom storefront and place orders on the Salesforce webstore programmatically.
- Orders into the ERP — Read order summaries for a buyer account after checkout and create the matching sales order in your ERP.
- Buyer account maintenance — Keep the buyer's shipping and billing addresses in sync with the master record held in your CRM or ERP.
B2B Commerce and D2C Commerce run on the Salesforce core platform, so their storefront APIs are Connect REST resources under /services/data — scoped to a webstore and acting for a buyer account: search the catalogue and read a product with the buyer's entitlements applied, build a cart, open and update a checkout, tokenise a payment method, post the payment and turn the checkout into an order, then read order summaries and manage the buyer's addresses. Apivom Atlas registers 17 of these routes, 5 read-only, together with the generic SOQL query endpoint and the SOAP partner API, all against your My Domain instance URL with a Connected App token. No Apivom product workflow uses Salesforce Commerce today — Apivom's ERP and order automation in production targets Penta and Autodesk, not a Salesforce webstore — so the connector is catalogued for merchants who run B2B or D2C Commerce and want an Apivom product scoped against their store.
A Connected App on your Salesforce org (consumer key + secret) and your My Domain instance URL. The caller runs the OAuth 2.0 flow and sends the access token as Bearer; the instance URL becomes the per-request base URL. 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 Commerce Cloud B2C (SFCC / Demandware)?
No. B2B/D2C Commerce lives on the Salesforce core platform and uses Connect REST under your My Domain. Commerce Cloud B2C — SLAS, Shopper APIs, OCAPI on commercecloud.salesforce.com — has its own connector in this catalogue.
Can orders flow into an Apivom-connected ERP?
Apivom's production ERP connectors are Penta and Autodesk PWS; a Salesforce Commerce to ERP flow has not been built. The routes are registered so it can be scoped with you per webstore.
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.