How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SAP Emarsys Email Reporting API

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.

SAP Emarsys Email Reporting API is one of 25 APIs that SAP Emarsys publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reporting, Delivery Results, and Email Analytics. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://api.emarsys.net.

1 operations 1 paths 2 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://api.emarsys.net/api/email/reporting/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

SAP Emarsys Email Reporting API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — To use this API, you must have an access token.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Operations 1
GET
/api/email/reporting/v1/contacts/{contactId}/deliveryResults
Get delivery results
indexAction_1 3 params → 200400401500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are DeliveryResult (4 properties), DeliveryResultsResponse (1 property). Each schema is shown below with its type and property counts.

DeliveryResultsResponse
object
1 property
DeliveryResult
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emarsys-email-reporting-api-openapi.yml Raw ↑

Other APIs SAP Emarsys publishes across the network.

SAP Emarsys Accounts API
SAP Emarsys Auto-import Profiles API
SAP Emarsys Bulk Response Summary API
SAP Emarsys Conditional Text Rules API
SAP Emarsys Contact and Email Data API
SAP Emarsys Contact Lists API
SAP Emarsys Contact Sources API
SAP Emarsys Contacts API
SAP Emarsys Email Campaign Lifecycle API
SAP Emarsys Email Campaigns API
SAP Emarsys Email Templates API
SAP Emarsys Events API
Where this information came from

This is an independent, third-party profile of SAP Emarsys Email Reporting API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.