b2c-scapi-shopper
Call Shopper Commerce APIs (SCAPI) from headless storefronts and composable commerce apps. Use this skill whenever the user is building with PWA Kit, Storefront Next (SFNext), or a headless frontend and needs to search products, manage baskets, submit orders, access customer data, or set shopper context. Also use when they ask about Shopper API authentication, checkout flows from a frontend app, or performance optimization for API calls — even if they just say "search products from my PWA" or "build a headless checkout".
How do I install this agent skill?
npx skills add https://github.com/salesforcecommercecloud/b2c-developer-tooling --skill b2c-scapi-shopperIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides documentation, architectural patterns, and code examples for integrating with Salesforce B2C Commerce Shopper APIs. It facilitates storefront operations like product search, basket management, and checkout flows using standard authentication and API interaction patterns.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerwarn
4/4 files flagged
What does this agent skill do?
Shopper Commerce APIs
Build storefront product, basket, checkout, customer, and context flows with SCAPI. For backend management use Admin APIs.
Tool choice
When B2C MCP is available:
- Read
skill://mcp/scapi/SKILL.mdonce through resources orskills_readbefore code-mode tools; passskillRead: true. scapi_searchwithauthType: "shopper"discovers bundled contracts offline. Find method/path/operationId first, then selected inputs, response fields, and security. Mixed Admin/Shopper operations can appear in either filter.- Shopper execution is unsupported in
scapi_execute; adding a SLAS client cannot enable it. Execute storefront flows through the application's Shopper SDK/client with the appropriate SLAS token flow. Prefer dedicated tools where available. scapi_schemas_listretrieves live tenant contracts and custom attributes;scapi_custom_apis_get_statuschecks custom registration. Code mode does not execute custom APIs.config_inspectreports configured values with masking.docs_search/docs_readanswer platform semantics, authentication, and limits; avoid duplicate contract reads.
CLI alternatives: b2c scapi schemas list,
b2c scapi schemas get <family> <name> <version>, and b2c setup inspect.
These schema commands use live Schemas API access; MCP discovery is offline.
Integration essentials
- Reuse configured shortCode, organizationId, and siteId; do not invent identifiers.
- Shopper authentication uses SLAS guest/registered flows and client scopes; Account Manager credentials are not a substitute. Keep private-client secrets and token exchange on the backend.
- Discover the contract for the selected API version. Examples are illustrative; verify version-specific behavior and limits in official docs.
- Preserve basket/order state and handle errors explicitly. Page/filter responses and return only fields needed by the next operation.
- For headless payment authorization, inspect order-PI hooks and order lifecycle before choosing a placement flow.
Conditional references
- Client examples: implementing auth and API calls.
- Checkout: basket-to-order workflow.
- Common patterns: errors, pagination, field selection.
- Scopes: Shopper grants by family.
- SLAS: CLI client management.
- Advanced auth: OTP, passkeys, session bridge.
- Official docs:
commerce-api/use-shopper-api,commerce-api/slas,commerce-api/work-with-baskets-orders,commerce-api/shopper-context-best-practices,commerce-api/auth-z-scope-catalog,commerce-api/performance.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-scapi-shopper">View b2c-scapi-shopper on skillZs</a>