B2C Content Skill

Use the b2c CLI to export, list, and validate Page Designer content from Salesforce B2C Commerce content libraries.

Tip: If b2c is not installed globally, use npx @salesforce/b2c-cli instead (e.g., npx @salesforce/b2c-cli content export homepage).

Configuration & Authentication

The CLI auto-discovers the target instance and credentials from SFCC_* environment variables (including project .env), the selected project-local or shared dw.json, and configuration plugins. package.json supplies only non-sensitive defaults. Flags like --server, --client-id, --client-secret, --username, and --password are usually unnecessary — only pass them to override what's auto-detected.

Run b2c setup inspect to see the resolved configuration and which source provided each value (use --json for scripting; secrets stay masked by default). For precedence rules and troubleshooting, see the b2c-cli:b2c-config skill.

Online export/list starts a system export job: SCAPI uses sfcc.jobs.rw plus the tenant scope; WebDAV downloads the archive and assets. --api-backend ocapi forces OCAPI; auto permits fallback. If an error only mentions OCAPI, retry with --api-backend scapi to expose the SCAPI failure before assuming OCAPI permissions are needed.

Examples

Export Pages