SAP Emarsys

SAP Emarsys (formerly Emarsys, acquired by SAP in 2020 and now marketed as part of SAP Engagement Cloud) is an omnichannel customer engagement and marketing automation platform used by retail and consumer brands to run personalized email, SMS, mobile, web and ads campaigns from a unified customer data layer with AI-driven segmentation. The developer surface is the Emarsys Core API — 23 published endpoint batches covering contacts and custom contact fields, static contact lists and rule-based segments, email campaign creation, preview, test-send, launch and stop, delivery status and response-metric reporting, external event triggers that start Automation Centre programs, media assets, tracked links, account and API-user administration, and the Relational Data Store (RDS) custom-object layer for purchase and product data. A separately published SMS Partner API lets SMS aggregators integrate with the Emarsys SMS channel. Authentication is the legacy X-WSSE UsernameToken header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 client credentials / OpenID Connect on the v3 surface. Rate limiting is 1000 requests per minute per API user with published X-RateLimit-* headers, and errors are returned as a proprietary replyCode/replyText/data envelope that can carry failures inside HTTP 200 responses.

SAP Emarsys publishes 25 APIs on the APIs.io network, including Accounts API, Auto-import Profiles API, Bulk Response Summary API, and 22 more. Tagged areas include Marketing Automation, Customer Engagement, Email Marketing, Omnichannel, and Customer Data Platform.

The SAP Emarsys catalog on APIs.io includes 1 event-driven AsyncAPI specification.

SAP Emarsys’ developer surface includes changelog, authentication, documentation, API reference, getting-started guide, pricing, support, and 38 more developer resources.

🌐 Visit website 📡 Source on GitHub

66.8/100 exemplar ▬ flat Agent 51/100 agent ready Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0

25 APIs

Marketing AutomationCustomer EngagementEmail MarketingOmnichannelCustomer Data PlatformSAPSegmentationSMSMarketing AnalyticsRetailPersonalizationCampaign Management

Kin Score

Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0

Composite quality — 66.8/100 · exemplar

Contract Quality 12.7 / 21

Developer Ergonomics 12.0 / 17

Access Clarity 9.2 / 17

Operational Transparency 7.3 / 11

Contract Governance 1.7 / 10

Discoverability 7.4 / 9

Regulatory Posture 12.1 / 15

Agent readiness — 51/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 3 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/emarsys: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 25

Individual APIs this provider publishes, each with its own machine-readable definition.

Open Collections 25

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Emarsys Scopes

156 scopes · clientCredentials

156 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Emarsys Agentic Access

136 operations · 80 acting · 1 human-in-the-loop

136 operations · 80 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SAP Help Portal

SAP Help Portal

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

LLMsTxt

AgentSkill

AgenticAccess

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Webhooks

Build 5

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

Postman

Postman

PostmanCollection

PostmanCollection

GitHubOrganization

GitHubOrganization

Access & Security 9

Authentication, authorization, and security posture

SecurityTxt

Compliance

TrustCenter

Authentication

OAuthScopes

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

DomainSecurity

DomainSecurity

Authentication

Authentication

Scroll for all 9

Operate 6

Status, limits, changes, and where to get help

StatusPage

Deprecation

ChangeLog

RateLimits

Support

HelpCenter

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

PrivacyPolicy

TermsOfService

Company 4

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

X (Twitter)

X (Twitter)

Other 1

Properties that don't map to a standard resource type

API Credentials

API Credentials

Source (apis.yml)

aid: emarsys
name: SAP Emarsys
description: SAP Emarsys (formerly Emarsys, acquired by SAP in 2020 and now marketed as part of SAP Engagement Cloud) is an
  omnichannel customer engagement and marketing automation platform used by retail and consumer brands to run personalized
  email, SMS, mobile, web and ads campaigns from a unified customer data layer with AI-driven segmentation. The developer
  surface is the Emarsys Core API — 23 published endpoint batches covering contacts and custom contact fields, static contact
  lists and rule-based segments, email campaign creation, preview, test-send, launch and stop, delivery status and response-metric
  reporting, external event triggers that start Automation Centre programs, media assets, tracked links, account and API-user
  administration, and the Relational Data Store (RDS) custom-object layer for purchase and product data. A separately published
  SMS Partner API lets SMS aggregators integrate with the Emarsys SMS channel. Authentication is the legacy X-WSSE UsernameToken
  header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 client credentials
  / OpenID Connect on the v3 surface. Rate limiting is 1000 requests per minute per API user with published X-RateLimit-*
  headers, and errors are returned as a proprietary replyCode/replyText/data envelope that can carry failures inside HTTP
  200 responses.
type: Index
accessModel:
  pricing: contact-sales
  onboarding: sales-gate
  trial: false
  try_now: false
  public: false
  label: Enterprise sales, no self-serve signup
  confidence: high
  source:
  - https://emarsys.com/request-pricing/
  - https://emarsys.com/demo/
  - plans/emarsys-plans-pricing.yml
  note: Corrected 2026-08-13 from a derived "self-serve signup" reading. SAP Emarsys publishes no price list and no signup
    path — emarsys.com/pricing/ now 404s and the only routes in are a "Request pricing" lead form and a demo request. API
    credentials are created by an account owner inside an existing Emarsys account (Admin > Security Settings), so there is
    no way for a developer to obtain access without a customer contract.
  generated: '2026-08-13'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/emarsys.png
tags:
- Marketing Automation
- Customer Engagement
- Email Marketing
- Omnichannel
- Customer Data Platform
- SAP
- Segmentation
- SMS
- Marketing Analytics
- Retail
- Personalization
- Campaign Management
url: https://raw.githubusercontent.com/api-evangelist/emarsys/refs/heads/main/apis.yml
created: '2026-05-11'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: emarsys:emarsys-accounts-api
  name: SAP Emarsys Accounts API
  description: In this batch you may find endpoints related to accounts. Published by SAP Emarsys as a Swagger 2.0 document
    with 10 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/43noz8h08gqdv-emarsys-core-api-accounts-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Account
  - Administrators
  - User Management
  - Access Levels
  tags_raw:
  - Accounts
  - Administrators
  - User Management
  - Access Levels
  properties:
  - type: OpenAPI
    url: openapi/emarsys-accounts-openapi.yml
  - type: Overlay
    url: overlays/emarsys-accounts-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/43noz8h08gqdv-emarsys-core-api-accounts-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-auto-import-profiles-api
  name: SAP Emarsys Auto-import Profiles API
  description: In this batch you may find endpoints related to auto-import profiles. Published by SAP Emarsys as a Swagger
    2.0 document with 4 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken
    header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect
    on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200
    responses, so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/vq6ozhk87xpct-emarsys-core-api-auto-import-profiles-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Auto-import
  - Data Import
  - Scheduling
  properties:
  - type: OpenAPI
    url: openapi/emarsys-auto-import-profiles-openapi.yml
  - type: Overlay
    url: overlays/emarsys-auto-import-profiles-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/vq6ozhk87xpct-emarsys-core-api-auto-import-profiles-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-bulk-response-summary-api
  name: SAP Emarsys Bulk Response Summary API
  description: In this chapter you may find the bulk response summary endpoint. Published by SAP Emarsys as OpenAPI 3.0.3
    with 1 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/b8bkfdpzdnrmn-bulk-response-summary
  baseURL: https://api.emarsys.net/api/email/reporting/v1
  tags:
  - Reporting
  - Email Analytics
  - Bulk
  properties:
  - type: OpenAPI
    url: openapi/emarsys-bulk-response-summary-openapi.yml
  - type: Overlay
    url: overlays/emarsys-bulk-response-summary-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/b8bkfdpzdnrmn-bulk-response-summary
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-conditional-text-rules-api
  name: SAP Emarsys Conditional Text Rules API
  description: In this batch you may find endpoints related to conditional text rules. Published by SAP Emarsys as a Swagger
    2.0 document with 1 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken
    header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect
    on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200
    responses, so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/f2udgdha9qqax-emarsys-core-api-conditional-text-rules-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Personalization
  - Conditional Content
  - Email
  properties:
  - type: OpenAPI
    url: openapi/emarsys-conditional-text-rules-openapi.yml
  - type: Overlay
    url: overlays/emarsys-conditional-text-rules-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/f2udgdha9qqax-emarsys-core-api-conditional-text-rules-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-contact-and-email-data-api
  name: SAP Emarsys Contact and Email Data API
  description: In this batch you may find endpoints related to contact and email data. Published by SAP Emarsys as a Swagger
    2.0 document with 7 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken
    header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect
    on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200
    responses, so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/jxv7xghhduivk-emarsys-core-api-contact-and-email-data-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Contacts
  - Email Analytics
  - Export
  properties:
  - type: OpenAPI
    url: openapi/emarsys-contact-and-email-data-openapi.yml
  - type: Overlay
    url: overlays/emarsys-contact-and-email-data-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/jxv7xghhduivk-emarsys-core-api-contact-and-email-data-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-contact-lists-api
  name: SAP Emarsys Contact Lists API
  description: In this batch you may find endpoints related to contact lists. Published by SAP Emarsys as a Swagger 2.0 document
    with 11 operation(s), 2 of them marked deprecated. Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE
    UsernameToken header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 /
    OpenID Connect on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear
    inside HTTP 200 responses, so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/czeg4wbctz2ey-emarsys-core-api-contact-lists-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Contact Lists
  - Audience
  - Segmentation
  properties:
  - type: OpenAPI
    url: openapi/emarsys-contact-lists-openapi.yml
  - type: Overlay
    url: overlays/emarsys-contact-lists-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/czeg4wbctz2ey-emarsys-core-api-contact-lists-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-contact-sources-api
  name: SAP Emarsys Contact Sources API
  description: In this batch you may find endpoints related to contact sources. Published by SAP Emarsys as a Swagger 2.0
    document with 2 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/nbmm6cavfbful-emarsys-core-api-contact-sources-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Contacts
  - Provenance
  - Data Quality
  properties:
  - type: OpenAPI
    url: openapi/emarsys-contact-sources-openapi.yml
  - type: Overlay
    url: overlays/emarsys-contact-sources-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/nbmm6cavfbful-emarsys-core-api-contact-sources-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-contacts-api
  name: SAP Emarsys Contacts API
  description: In this batch you may find endpoints related to contacts. Published by SAP Emarsys as a Swagger 2.0 document
    with 7 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/vhlytrvjmpva3-emarsys-core-api-contacts-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Contacts
  - Customer Data
  - CRM
  properties:
  - type: OpenAPI
    url: openapi/emarsys-contacts-openapi.yml
  - type: Overlay
    url: overlays/emarsys-contacts-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/vhlytrvjmpva3-emarsys-core-api-contacts-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-email-campaign-lifecycle-api
  name: SAP Emarsys Email Campaign Lifecycle API
  description: In this batch you may find endpoints related to email campaign lifecycle. Published by SAP Emarsys as a Swagger
    2.0 document with 13 operation(s), 1 of them marked deprecated. Part of the SAP Emarsys Core API. Authentication is the
    legacy X-WSSE UsernameToken header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour
    of OAuth 2.0 / OpenID Connect on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope
    and can appear inside HTTP 200 responses, so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/111vbiacis1pw-emarsys-core-api-email-campaign-lifecycle-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Email
  - Campaign Launch
  - Delivery Status
  - Reporting
  properties:
  - type: OpenAPI
    url: openapi/emarsys-email-campaign-lifecycle-openapi.yml
  - type: Overlay
    url: overlays/emarsys-email-campaign-lifecycle-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/111vbiacis1pw-emarsys-core-api-email-campaign-lifecycle-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-email-campaigns-api
  name: SAP Emarsys Email Campaigns API
  description: In this batch you may find endpoints related to email campaigns. Published by SAP Emarsys as a Swagger 2.0
    document with 13 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/9mp221uux5ijk-emarsys-core-api-email-campaigns-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Email
  - Campaigns
  - Marketing Automation
  properties:
  - type: OpenAPI
    url: openapi/emarsys-email-campaigns-openapi.yml
  - type: Overlay
    url: overlays/emarsys-email-campaigns-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/9mp221uux5ijk-emarsys-core-api-email-campaigns-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-email-reporting-api-api
  name: SAP Emarsys Email Reporting API
  description: This document contains all of the email reporting related API endpoints. Published by SAP Emarsys as OpenAPI
    3.0.1 with 1 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/jntjf6yd8bbyp-email-reporting-api
  baseURL: https://api.emarsys.net/api/email/reporting/v1
  tags:
  - Reporting
  - Delivery Results
  - Email Analytics
  properties:
  - type: OpenAPI
    url: openapi/emarsys-email-reporting-api-openapi.yml
  - type: Overlay
    url: overlays/emarsys-email-reporting-api-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/jntjf6yd8bbyp-email-reporting-api
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-email-templates-api
  name: SAP Emarsys Email Templates API
  description: In this batch you may find endpoints related to email templates. Published by SAP Emarsys as a Swagger 2.0
    document with 2 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/ywep93d8zjj38-emarsys-core-api-email-templates-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Email
  - Templates
  - Content
  properties:
  - type: OpenAPI
    url: openapi/emarsys-email-templates-openapi.yml
  - type: Overlay
    url: overlays/emarsys-email-templates-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/ywep93d8zjj38-emarsys-core-api-email-templates-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-events-api
  name: SAP Emarsys Events API
  description: In this batch you may find endpoints related to events. Published by SAP Emarsys as a Swagger 2.0 document
    with 8 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/a9elofmiccck4-emarsys-core-api-events-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Event
  - Triggers
  - Real-Time
  - Automation
  tags_raw:
  - Events
  - Triggers
  - Real-time
  - Automation
  properties:
  - type: OpenAPI
    url: openapi/emarsys-events-openapi.yml
  - type: Overlay
    url: overlays/emarsys-events-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/a9elofmiccck4-emarsys-core-api-events-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-external-content-api
  name: SAP Emarsys External Content API
  description: In this batch you may find endpoints related to External Content. Published by SAP Emarsys as a Swagger 2.0
    document with 1 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/7nxw96vrmb8uy-emarsys-core-api-external-content-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Personalization
  - External Content
  - Integration
  properties:
  - type: OpenAPI
    url: openapi/emarsys-external-content-openapi.yml
  - type: Overlay
    url: overlays/emarsys-external-content-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/7nxw96vrmb8uy-emarsys-core-api-external-content-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-fields-api
  name: SAP Emarsys Fields API
  description: In this batch you may find endpoints related to fields. Published by SAP Emarsys as a Swagger 2.0 document
    with 6 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/mtzemy547drl7-emarsys-core-api-fields-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Contact Fields
  - Schema
  - Custom Fields
  properties:
  - type: OpenAPI
    url: openapi/emarsys-fields-openapi.yml
  - type: Overlay
    url: overlays/emarsys-fields-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/mtzemy547drl7-emarsys-core-api-fields-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-forms-api
  name: SAP Emarsys Forms API
  description: In this batch you may find endpoints related to forms. Published by SAP Emarsys as a Swagger 2.0 document with
    2 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which SAP
    Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/k53pb4h4cekls-emarsys-core-api-forms-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Forms
  - Lead Capture
  - Registrations
  properties:
  - type: OpenAPI
    url: openapi/emarsys-forms-openapi.yml
  - type: Overlay
    url: overlays/emarsys-forms-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/k53pb4h4cekls-emarsys-core-api-forms-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-keys-api
  name: SAP Emarsys Keys API
  description: In this batch you may find endpoints related to keys. Published by SAP Emarsys as a Swagger 2.0 document with
    4 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which SAP
    Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/j2c7sbanej44c-emarsys-core-api-keys-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Encryption
  - Key Management
  - Security
  properties:
  - type: OpenAPI
    url: openapi/emarsys-keys-openapi.yml
  - type: Overlay
    url: overlays/emarsys-keys-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/j2c7sbanej44c-emarsys-core-api-keys-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-media-database-api
  name: SAP Emarsys Media Database API
  description: In this batch you may find endpoints related to the Media Database. Published by SAP Emarsys as a Swagger 2.0
    document with 6 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/o26j9gs8fjm9q-emarsys-core-api-media-database-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Media
  - Assets
  - Digital Asset Management
  properties:
  - type: OpenAPI
    url: openapi/emarsys-media-database-openapi.yml
  - type: Overlay
    url: overlays/emarsys-media-database-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/o26j9gs8fjm9q-emarsys-core-api-media-database-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-programs-api
  name: SAP Emarsys Programs API
  description: In this batch you may find endpoints related to programs. Published by SAP Emarsys as a Swagger 2.0 document
    with 3 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/mzyq7rihy8uv9-emarsys-core-api-programs-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Automation Centre
  - Programs
  - Journeys
  properties:
  - type: OpenAPI
    url: openapi/emarsys-programs-openapi.yml
  - type: Overlay
    url: overlays/emarsys-programs-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/mzyq7rihy8uv9-emarsys-core-api-programs-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-relational-data-api
  name: SAP Emarsys Relational Data (RDS) API
  description: In this batch you may find endpoints related to Relational Data. Published by SAP Emarsys as a Swagger 2.0
    document with 6 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header,
    which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the
    v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses,
    so callers must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/0h26fkyuh837z-emarsys-core-api-relational-data-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Relational Data
  - Custom Objects
  - Product Data
  - Purchase Data
  properties:
  - type: OpenAPI
    url: openapi/emarsys-relational-data-openapi.yml
  - type: Overlay
    url: overlays/emarsys-relational-data-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/0h26fkyuh837z-emarsys-core-api-relational-data-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-sections-api
  name: SAP Emarsys Sections API
  description: In this batch you may find endpoints related to sections. Published by SAP Emarsys as a Swagger 2.0 document
    with 5 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/14tmor5bfxbov-emarsys-core-api-sections-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Email
  - Content Blocks
  - Templates
  properties:
  - type: OpenAPI
    url: openapi/emarsys-sections-openapi.yml
  - type: Overlay
    url: overlays/emarsys-sections-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/14tmor5bfxbov-emarsys-core-api-sections-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-segments-api
  name: SAP Emarsys Segments API
  description: In this batch you may find endpoints related to segments. Published by SAP Emarsys as a Swagger 2.0 document
    with 11 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which
    SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface.
    Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers
    must inspect replyCode rather than the status code.
  humanURL: https://dev.emarsys.com/docs/core-api-reference/ehr0tded4ctcw-emarsys-core-api-segments-endpoint-batch
  baseURL: https://api.emarsys.net/api
  tags:
  - Segmentation
  - Audience
  - Filters
  properties:
  - type: OpenAPI
    url: openapi/emarsys-segments-openapi.yml
  - type: Overlay
    url: overlays/emarsys-segments-overlay.yaml
  - type: Documentation
    url: https://dev.emarsys.com/
  - type: APIReference
    url: https://dev.emarsys.com/docs/core-api-reference/ehr0tded4ctcw-emarsys-core-api-segments-endpoint-batch
  - type: Authentication
    url: https://dev.emarsys.com/docs/emarsys-core-api-guides/b3c3a1eba8515-authentication
- aid: emarsys:emarsys-sms-partner-callbacks-api
  name: SAP Emarsys SMS Partner Callbacks API
  description: Published by SAP Emarsys as OpenAPI 3.0.3 with 2 operation(s). Part of the SMS Partner API, which SAP Emarsys
    publishes openly at github.com/emartech/sms-partner-api-spec so SMS aggregation partners can integrate with the Emarsys
    SMS channel. Authentication is OAuth 2.0 client credentials against SAP Identity Authentication Service.
  humanURL: https://emartech.github.io/sms-partner-api-spec/
  baseURL: https://api.emarsys.net/sms/partner/v1
  tags:
  - SMS
  - Webhook
  - Delivery Reports
  - Inbound Messages
  tags_raw:
  - SMS
  - Webhooks
  - Delivery Reports
  - Inbound Messa

# --- truncated at 32 KB (38 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/emarsys/refs/heads/main/apis.yml