From b2c-cli
Browses and retrieves SCAPI OpenAPI schema specifications for Salesforce B2C Commerce. Helps list APIs, inspect endpoints, request/response shapes, and data models.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b2c-cli:b2c-scapi-schemasThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `b2c` CLI plugin to browse and retrieve SCAPI OpenAPI schema specifications.
Use the b2c CLI plugin to browse and retrieve SCAPI OpenAPI schema specifications.
Tip: If
b2cis not installed globally, usenpx @salesforce/b2c-cliinstead (e.g.,npx @salesforce/b2c-cli scapi schemas list).
Values like tenantId, shortCode, clientId, and clientSecret resolve from dw.json / SFCC_* env vars / the active instance / configuration plugins. Examples below show minimal usage; add flags only to override configured values — passing --client-id/--client-secret/--tenant-id/--short-code is usually unnecessary. If a required value is missing, the CLI emits an actionable error pointing at the flag, env var, and config key.
Run b2c setup inspect to see the resolved configuration and which source provided each value (--json for scripting, --unmask to reveal secrets). For precedence rules and troubleshooting, see the b2c-cli:b2c-config skill.
The tenant ID identifies your B2C Commerce instance for SCAPI calls. It is not the same as the organization ID:
zzxy_prd (the tenantId value in dw.json, or --tenant-id override)f_ecom_zzxy_prd (used in SCAPI URLs, has f_ecom_ prefix)For sandbox instances, derive the tenant ID from the hostname by replacing hyphens with underscores:
| Hostname | Tenant ID |
|---|---|
zzpq-013.dx.commercecloud.salesforce.com | zzpq_013 |
zzxy-001.dx.commercecloud.salesforce.com | zzxy_001 |
abcd-dev.dx.commercecloud.salesforce.com | abcd_dev |
For production instances, use your realm and instance identifier (e.g., zzxy_prd).
# list all available SCAPI schemas (uses configured tenant)
b2c scapi schemas list
# list with JSON output
b2c scapi schemas list --json
# target a different tenant than the active config
b2c scapi schemas list --tenant-id zzxy_prd
# filter by API family (e.g., product, checkout, search)
b2c scapi schemas list --api-family product
# filter by API name
b2c scapi schemas list --api-name shopper-products
# filter by status
b2c scapi schemas list --status current
By default, schemas are output in a collapsed format optimized for context efficiency. This is ideal for agentic use cases and LLM consumption.
# get collapsed schema (paths show methods, schemas show names only)
b2c scapi schemas get product shopper-products v1
# save to file
b2c scapi schemas get product shopper-products v1 > schema.json
Expand only the parts of the schema you need:
# expand specific paths
b2c scapi schemas get product shopper-products v1 --expand-paths /products,/products/{productId}
# expand specific schemas
b2c scapi schemas get product shopper-products v1 --expand-schemas Product,ProductResult
# combine expansions
b2c scapi schemas get product shopper-products v1 --expand-paths /products --expand-schemas Product
# get full schema without any collapsing
b2c scapi schemas get product shopper-products v1 --expand-all
Discover what's available in a schema before expanding:
# list all paths in the schema
b2c scapi schemas get product shopper-products v1 --list-paths
# list all schema names
b2c scapi schemas get product shopper-products v1 --list-schemas
# list all examples
b2c scapi schemas get product shopper-products v1 --list-examples
# output as YAML
b2c scapi schemas get product shopper-products v1 --yaml
# output wrapped JSON with metadata (apiFamily, apiName, apiVersion, schema)
b2c scapi schemas get product shopper-products v1 --json
# include custom properties (default behavior)
b2c scapi schemas get product shopper-products v1
# exclude custom properties
b2c scapi schemas get product shopper-products v1 --no-expand-custom-properties
The tenant ID and short code can be overridden via flags or environment variables:
--tenant-id / SFCC_TENANT_ID / tenantId in dw.json--short-code / SFCC_SHORTCODE / shortCode in dw.jsonSee b2c scapi schemas --help for a full list of available commands and options.
npx claudepluginhub salesforcecommercecloud/b2c-developer-tooling --plugin b2c-cliSearches and reads B2C Commerce documentation across Script API, Developer Center, Salesforce Help, tooling, job steps, and XSD schemas. Use for any B2C Commerce developer or administrator question.
Develops Custom SCAPI REST endpoints with api.json routes, schema.yaml definitions, and OAuth scope configuration. Helps debug endpoint registration and 404 issues for Salesforce B2C Commerce.
Documents OCAPI Shop and Data API endpoints, authentication, pagination, and SCAPI migration guide for maintaining legacy Salesforce B2C Commerce integrations.