sfcc-ocapi-scapi

Integrate Salesforce Commerce Cloud headless APIs for storefront and mobile commerce.

44|7|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill sfcc-ocapi-scapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfcc-ocapi-scapi
Source: https://github.com/finsilabs/awesome-ecommerce-skills/tree/main/skills/platform-salesforce-cc/sfcc-ocapi-scapi
Command: npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill sfcc-ocapi-scapi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables developers to integrate with Salesforce Commerce Cloud's headless APIs (OCAPI and Shopper APIs) for building custom storefronts and mobile commerce experiences, overcoming the limitations of traditional monolithic architectures.

Core Features & Use Cases

  • Headless Storefronts: Build modern, composable storefronts using SCAPI (Shopper APIs).
  • Mobile Commerce: Integrate mobile applications with SFCC product catalog, cart, and checkout.
  • Admin Operations: Manage products, orders, and promotions using OCAPI Data API.
  • API Landscape Understanding: Differentiates between SCAPI and OCAPI for appropriate use cases.

Quick Start

Use the sfcc-ocapi-scapi skill to authenticate with SLAS and retrieve a guest access token for making Shopper API calls.

Frequently Asked Questions about sfcc-ocapi-scapi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate with Salesforce Commerce Cloud headless APIs for a custom storefront?

To authenticate with Salesforce Commerce Cloud headless APIs, you use SLAS (Shopper Login and API Access Service) to retrieve a guest access token for making Shopper API calls, and client credentials for OCAPI Data API access.

What is the difference between SCAPI and OCAPI for SFCC integration?

SCPI provides Shopper APIs for building modern, composable headless storefronts and mobile commerce, while OCAPI Data API is used for admin operations like managing products, orders, and promotions in Salesforce Commerce Cloud.

Can I manage product catalogs and process orders using SFCC headless APIs?

Yes, you can manage product catalogs, execute cart operations, and process orders by integrating with Salesforce Commerce Cloud headless APIs using the appropriate SCAPI Shopper endpoints and OCAPI Data API credentials.

How do I get a guest access token for SFCC Shopper API calls?

You obtain a guest access token for SFCC Shopper API calls by authenticating through SLAS, enabling your custom storefront or mobile commerce application to interact with the product catalog and cart.

When should I use SFCC headless APIs instead of a traditional monolithic architecture?

You should use SFCC headless APIs when you need to build modern, composable storefronts or mobile commerce experiences that overcome the limitations of traditional monolithic architectures.

Does this approach support mobile commerce integration with Salesforce Commerce Cloud?

Yes, this approach supports mobile commerce integration by using SCAPI Shopper APIs to connect mobile applications directly with the SFCC product catalog, cart operations, and checkout processes.