Headless 360Intermediateexperience-cloudself-serviceapiportal
Build headless self-service portal on Experience Cloud APIs
Real World Scenario
Customers want a custom React portal for case management and knowledge search instead of standard Experience Cloud templates.
Expected Answer
• Use Experience Cloud headless with User Access APIs and CMS delivery APIs
• Authenticate via OAuth with community user context preserving sharing rules
• Headless CMS for knowledge articles with structured content APIs
• Case create/update via UI API or dedicated REST respecting entitlements
• Embed Agentforce messaging SDK for support chat in custom UI
• Theming and localization handled client-side with CMS content keys
• SEO and SSR considerations if portal pages must be indexed
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Use Experience Cloud headless with User Access APIs and CMS delivery APIs. Authenticate via OAuth with community user context preserving sharing rules. Pick based on your integration pattern and team capability. Headless Experience Cloud still enforces Salesforce authorization—custom UI does not bypass sharing. Balance speed of delivery with maintainability.
Architect Perspective
Headless Experience Cloud still enforces Salesforce authorization—custom UI does not bypass sharing.