SLAS Support for Custom Parameters and Hooks

Custom parameters can be passed to the following SLAS endpoints:

Make sure you prefix the parameter names with c_.

  • For the /login endpoint, SLAS forwards custom c_-prefixed headers (with values matching [a-zA-Z0-9-._]) to the B2C Commerce platform.
  • There are no SCAPI hooks for the /login and /authorize endpoints. /login runs /customers/auth hooks and /authorize runs no hooks.

Note

Announcements
Choose Your B2C Commerce Storefront Type
Universal Commerce Protocol (UCP) Integration
B2C Commerce
SCAPI
Why Use SCAPI
Base URL and Request Formation
Authorization
Quick Start
General Guidance
Develop
Use SCAPI with MuleSoft
Use the Admin API
Use the Shopper API
Shopper Login (SLAS)
Public Client Use Cases
Private Client Use Cases
SLAS Best Practices
Log Out Multiple Shoppers
Identity Providers
Validate SLAS JWTs
Session Bridge Overview
Trusted Agent Authorization
Trusted System on Behalf Authorization
Passwordless Login
Password Reset with Callback URI
Password Reset with Email
Custom Parameters and Hooks
Merge Shopper Profiles
Manage Shopper Tracking Preferences
Shopper Context
Build Baskets and Place Orders
Guest Order Access with an Access Code (OTP)
Promotion Types and Requirements
Agentic MCP Shopper Tools Quick Start (Pilot)
URL Mapping
Extend
Secure Your Site
Optimize Performance
Troubleshoot
SCAPI Specifications
Agentforce Commerce Vibes
Storefront Next
Composable Storefront
Storefront Reference Architecture (SFRA)
Agentforce Commerce Client
Commerce Apps ISV Developer Guide
B2C Commerce Solutions
B2C Commerce Release Notes
B2C Commerce Reference Information
Ask the Community