SAP Emarsys · Authentication Profile

Emarsys Authentication

Authentication

SAP Emarsys secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Marketing AutomationCustomer EngagementEmail MarketingOmnichannelCustomer Data PlatformSAP
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

WSSE apiKey
· in: header (X-WSSE)
OAuth2 oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/emarsys-openapi.yml
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: WSSE
  type: apiKey
  in: header
  parameter: X-WSSE
  description: Legacy WSSE authentication header (being deprecated).
  sources:
  - openapi/emarsys-openapi.yml
- name: OAuth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.emarsys.net/api/v3/auth/token
    scopes: 0
  sources:
  - openapi/emarsys-openapi.yml