Integration23% of the exam

Choosing APIs for Commerce, Engagement and service

Which API or protocol to use when integrating with B2C Commerce (SCAPI, OCAPI, WebDAV feeds and jobs), the Salesforce service org (platform events, Connect REST API, Order Management data) and Marketing Cloud Engagement (REST, SOAP, server-to-server auth and Event Notification Service), and the behaviours each one brings.

Official exam objective
Understand the recommended methods on how to integrate systems to Agentforce Service, B2C Commerce, and Marketing Cloud environments using APIs and protocols that support various integration design patterns.

~8 min read · 17 practice questions

What the exam expects

  • Choose SCAPI for a new B2C Commerce build, use Shopper Context instead of hand-written hooks, and authenticate requests in an existing OCAPI integration correctly.
  • Move feeds in and out of B2C Commerce with WebDAV, transfer scripts and job flows, with the right credential.
  • Pick the Salesforce platform API for publishing events, reading CMS content and creating orders beside the B2C Commerce integration.
  • Integrate with Marketing Cloud Engagement through REST and SOAP, server-to-server tokens and Event Notification Service.
  • Route service-org email and web intake within their per-user and record-type rules.

Key terms:

  • SCAPI: the B2C Commerce API, a set of stateless REST APIs introduced in 2020 for headless commerce.
  • OCAPI: Open Commerce API, the older B2C Commerce API (Shop and Data APIs) in the platform since 2014.
  • WebDAV Impex share: the instance's Impex/src folder that external systems upload feeds to.
  • Installed Packages: the Engagement Setup page where an API integration gets its client ID and secret.
  • Event Notification Service (ENS): an Engagement service that pushes events such as email unsubscribes to a registered HTTPS callback.

Key facts

SLAS during migration
Detail
One token works across OCAPI and SCAPI
Easiest secure automated upload
Detail
HTTPS PUT to WebDAV Impex/src
FTPClient
Detail
Sandboxes only; firewall rule from Support
Sibling flows
Detail
Run in parallel when resources allow
Platform event publish success
Detail
Request queued; published asynchronously
Delete change event (Pub/Sub API)
Detail
All fields present with empty values
Engagement token after integration change
Detail
Up to five minutes
ENS delivery
Detail
At least once; nothing replayed for a paused period
Emails one person can send
Detail
250 per hour, each recipient counted
Sources for this section (9)
  • In what order do sibling job flows run when they're configured to execute sequentially?
  • Why can an FTP call from a B2C Commerce script run longer than the value passed to FTPClient.setTimeout?
  • Which permissions does an Engagement API integration need before it can use Event Notification Service?
  • When should a third party reach a private file-transfer pipeline through a public subpipeline?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the B2C Solution Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 20 lessons of the B2C Solution Architect guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Practice exams purchase adds inline bank questions and topic practice (17 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Choose guide-only, practice-only, or save $4 with both

Practice for the B2C Solution Architect exam