SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsb2c-scapi-shopper

b2c-scapi-shopper

Coding & development

View repository

Updated 10-15 23:57

About this skill

Shopper Commerce APIs

Build storefront product, basket, checkout, customer, and context flows with SCAPI. For backend management use the b2c-scapi-admin skill.

Tool choice

When B2C MCP is available:

  • Read skill://mcp/b2c-mcp-scapi/SKILL.md once through resources or skills_read before code-mode tools; pass skillRead: true.
  • scapi_search with authType: "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_list retrieves live tenant contracts and custom attributes; scapi_custom_apis_get_status checks custom registration. Code mode does not execute custom APIs.
  • config_inspect reports configured values with masking. docs_search/docs_read answer 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 the order-PI hooks in the b2c-hooks skill ("Headless Order Payment") and the order lifecycle in the b2c-ordering skill 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.
  • b2c-slas skill: CLI client management.
  • b2c-slas-auth-patterns skill: 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.