Salesforce Decode
Salesforcedecode
Back to questions
Headless 360Architect (Hardest)agentforceapiembeddingpartners

Embed Agentforce session APIs in third-party partner portals

Real World Scenario

Logistics partners embed support agent in their shipper portal helping customers track Salesforce-stored shipments without visiting your brand site.

Expected Answer

• Use Agentforce session API creating authenticated sessions scoped to partner OAuth client • Pass verified customer context token from partner auth—not partner user guessing customer IDs • Restrict agent topics and actions to shipment domain preventing cross-customer data access • Render agent UI via embedded widget or headless message API matching partner design system • Log partner client ID with every session for audit and abuse detection • Define SLAs and rate limits per partner tier in API gateway • Fallback to case creation API when agent unavailable with structured context from session

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Use Agentforce session API creating authenticated sessions scoped to partner OAuth client. Pass verified customer context token from partner auth—not partner user guessing customer IDs. Pick based on your integration pattern and team capability. Embedded agents in partner apps are B2B2C trust boundaries—scope sessions narrowly and audit partner context injection. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Embedded agents in partner apps are B2B2C trust boundaries—scope sessions narrowly and audit partner context injection.