Included because its Core API exposes contacts, segments, campaigns, events, products, orders, and reporting for omnichannel interfaces while SAP Emarsys moves the API from legacy WSSE toward OAuth/OIDC authentication.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Contacts and fields, contact lists and segments, email campaigns and schedules, external events, automation programs, products and orders, email-response metrics, and supported SMS or loyalty resources on their separate API families.
Read permitted contacts and fields, list or segment membership and counts, campaign state, external-event configuration, product or order data, and email engagement or deliverability results.
Create or update contacts and audience data, create or control supported email campaigns, and trigger enabled external events or transactional workflows through the appropriate API family.
Core API v3 uses OAuth 2.0 with OpenID Connect and JWT. Legacy WSSE authentication is deprecated for a final sunset at the end of 2026, so the required credential model depends on the endpoint batch during migration.
Pin each integration to an endpoint batch and authentication mode, keep contact identity and audience scope visible, and require a preview before campaign control, external-event triggers, or transactional actions that can reach customers immediately.
No Emarsys-native provider MCP is documented. Authentication and resource coverage vary by API family and endpoint batch during the WSSE-to-OAuth transition, and enabled modules still determine available operations.
First-party access
Agent access
Support: Bridge
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that SAP ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party developer documentation or platform overview.
Targeted first-party core-access review
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
