Does this skill support both JSON and YAML?

Yes, while JSON is often the default, you can use the --yaml flag to retrieve schema specifications in YAML format.

What is the difference between the Tenant ID and Organization ID?

The Tenant ID is a short identifier (e.g., zzxy_prd) required for CLI commands, whereas the Organization ID (e.g., f_ecom_zzxy_prd) includes an 'f_ecom_' prefix and is used specifically in SCAPI URLs.

How can I reduce token usage when viewing large API schemas?

The skill defaults to a collapsed output. Use the --expand-paths or --expand-schemas flags to view only the specific parts of the API you are currently working on.

Can I derive my Tenant ID from my Salesforce sandbox URL?

Yes, you can derive the Tenant ID by replacing hyphens with underscores in your hostname (e.g., zzxy-001.dx.commercecloud.salesforce.com becomes zzxy_001).

Salesforce B2C SCAPI Schemas

Name: Salesforce B2C SCAPI Schemas
Author: SalesforceCommerceCloud

bySalesforceCommerceCloud

•

E-commerce Solutions

Explores and retrieves OpenAPI schema specifications for Salesforce B2C Commerce APIs to streamline commerce integration and development.

About

The b2c-scapi-schemas skill enables developers to browse and retrieve Salesforce B2C Commerce API (SCAPI) specifications directly within their terminal. It facilitates the discovery of endpoints, request/response formats, and data models across API families like product, checkout, and search. Designed for efficiency, it offers unique schema-collapsing features that provide Claude with high-context API documentation while minimizing token usage, allowing for precise selective expansion of paths and schemas during the development of B2C Commerce solutions.

Key Features

Retrieve LLM-optimized collapsed schemas to preserve context window
List and filter SCAPI schemas by API family, name, or status
8 GitHub stars
Identify available endpoints and data models without loading full specifications
Support for JSON and YAML output formats with metadata wrapping
Selectively expand specific API paths or schema definitions as needed

Use Cases

Verifying specific request and response structures during integration debugging
Extracting precise data models for custom B2C Commerce frontend implementations
Exploring available SCAPI endpoints when architecting new commerce features

About

Key Features

Retrieve LLM-optimized collapsed schemas to preserve context window
List and filter SCAPI schemas by API family, name, or status
8 GitHub stars
Identify available endpoints and data models without loading full specifications
Support for JSON and YAML output formats with metadata wrapping
Selectively expand specific API paths or schema definitions as needed

Use Cases

Verifying specific request and response structures during integration debugging
Extracting precise data models for custom B2C Commerce frontend implementations
Exploring available SCAPI endpoints when architecting new commerce features