sfcc-ocapi-scapi-slas

Guide OCAPI versus SCAPI selection and SLAS token lifecycle management for SFCC integrations.

27|9|Updated Aug 8, 2025

Search Tags:#authentication #integration #oauth #slas #scapi #sfcc #ocapi

Ready to run

npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-ocapi-scapi-slas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sfcc-ocapi-scapi-slas
Source: https://github.com/taurgis/sfcc-dev-mcp/tree/main/ai-instructions/skills/sfcc-ocapi-scapi-slas
Command: npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-ocapi-scapi-slas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decision guidance for selecting OCAPI vs SCAPI and handling SLAS token lifecycle implications (guest tokens, rotation, public vs private clients, and hybrid SFRA/headless auth) to prevent auth pitfalls and rate-limit issues.

Core Features & Use Cases

Framework for OCAPI vs SCAPI decision to optimize storefront vs admin API access.
SLAS token lifecycle guidance covering guest tokens, refresh rotation, and client type selection.
Hybrid authentication considerations for SFRA/headless setups ensuring compatibility and correct scope.

Quick Start

Provide a decision framework for choosing OCAPI vs SCAPI and outline SLAS token lifecycle steps for a storefront integration.

Frequently Asked Questions about sfcc-ocapi-scapi-slas

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

FAQPage Schema

When should I use OCAPI vs SCAPI for Salesforce Commerce Cloud integration?▼

OCAPI vs SCAPI selection depends on your storefront vs admin API access requirements. OCAPI suits traditional storefront integrations, while SCAPI is optimized for headless commerce and modern API-first architectures within SFCC environments.

How do I manage SLAS token lifecycle for guest users in a headless SFCC setup?▼

SLAS token lifecycle management for guest users involves acquiring guest tokens and handling refresh rotation. This ensures continuous authentication access in headless SFCC setups without requiring repeated user logins.

What is the difference between public and private SLAS client types for SFCC authentication?▼

Public SLAS clients are used for storefront scenarios where client secrets cannot be securely stored, while private clients are for backend integrations requiring higher privilege and secure secret management for SFCC authentication.

How do I troubleshoot SLAS authentication and rate-limit issues across SFCC APIs?▼

Troubleshooting SLAS authentication and rate-limit issues involves analyzing token lifetimes, refresh rotation patterns, and client-type selection to identify misconfigurations causing API throttling or access failures in SFCC.

Can I use SLAS authentication for a hybrid SFRA and headless storefront implementation?▼

Yes, SLAS supports hybrid SFRA and headless authentication setups. It provides guidance on ensuring compatibility and correct scope across both architectures to maintain a unified authentication experience.