SAP Emarsys

SAP Emarsys Delivery Reports API

The Delivery Reports API from SAP Emarsys — 1 operation(s) for delivery reports.

Documentation GitHub OpenAPI

Operations 1

POST /clients/{clientId}/deliveryReports Delivery reports callback #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/emarsys-delivery-reports-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  version: 0.0.1
  title: Provider callbacks Delivery Reports API
  description: 'An SAP Emarsys SMS Partner Service allows partners to host SMS message sends that are triggered

    by an SAP Emarsys SMS campaign launch. This OpenAPI specification describes the possible callback endpoints.'
  contact:
    name: SAP Emarsys SMS Team
    email: team-sms@emarsys.com
servers:
- url: https://api.emarsys.net/sms/partner/v1
security:
- oAuthAuthorization: []
tags:
- name: Delivery Reports
paths:
  /clients/{clientId}/deliveryReports:
    post:
      summary: Delivery reports callback
      operationId: sendDeliveryReports
      tags:
      - Delivery Reports
      security:
      - oAuthAuthorization: []
      parameters:
      - $ref: ./common.yaml#/components/parameters/clientIdPathParam
      requestBody:
        description: The body of the delivery reports in JSON format
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeliveryReportBatch'
      responses:
        '202':
          $ref: ./common.yaml#/components/responses/AcceptedResponse
        '400':
          $ref: ./common.yaml#/components/responses/InvalidFormatResponse
        '401':
          $ref: ./common.yaml#/components/responses/AuthenticationFailedResponse
        '403':
          $ref: ./common.yaml#/components/responses/AuthorizationFailedResponse
        '404':
          $ref: ./common.yaml#/components/responses/ClientDoesNotExistResponse
        '429':
          $ref: ./common.yaml#/components/responses/TooManyRequestsResponse
        5XX:
          $ref: ./common.yaml#/components/responses/ServerErrorResponse
components:
  schemas:
    DeliveryReport:
      allOf:
      - $ref: ./common.yaml#/components/schemas/ReceivedAt
      - $ref: ./common.yaml#/components/schemas/EmarsysMessageId
      - type: object
        properties:
          status:
            type: string
            enum:
            - ACCEPTED
            - DELIVERED
            - SOFTBOUNCE
            - HARDBOUNCE
            - UNKNOWN
            - ERROR
            example: DELIVERED
          details:
            description: This property can be used to provide extra details about the status of the delivery
            type: object
            example:
              providerStatus: HARDBOUNCE
              providerCode: 5001
          providerMessageIds:
            type: array
            items:
              type: string
              example: yqqKUsSSvr
              description: Original provider (vendor) message ID, used for troubleshooting directly with the vendor
            minItems: 1
            description: Original message IDs from the provider (vendor) can be used to aid troubleshooting with the provider
    DeliveryReportSuccess:
      allOf:
      - $ref: '#/components/schemas/DeliveryReport'
      - type: object
        properties:
          status:
            type: string
            enum:
            - ACCEPTED
            - DELIVERED
            - SOFTBOUNCE
            - HARDBOUNCE
            - UNKNOWN
            example: DELIVERED
        required:
        - status
    DeliveryReportError:
      allOf:
      - $ref: '#/components/schemas/DeliveryReport'
      - type: object
        properties:
          status:
            type: string
            enum:
            - ERROR
            example: ERROR
          errorType:
            type: string
            enum:
            - AUTHENTICATION
            - INVALID_SENDER_ID
            - INSUFFICIENT_CREDIT
            - UNKNOWN
            example: AUTHENTICATION
            description: Type of the error. Used to determine how the user is notified.
        required:
        - status
        - errorType
    DeliveryReportBatch:
      type: object
      properties:
        deliveryReports:
          type: array
          items:
            oneOf:
            - $ref: '#/components/schemas/DeliveryReportSuccess'
            - $ref: '#/components/schemas/DeliveryReportError'
          minItems: 1
          maxItems: 1000
      required:
      - deliveryReports
  securitySchemes:
    oAuthAuthorization:
      type: oauth2
      description: OAuth client credentials grant type authorization
      flows:
        clientCredentials:
          tokenUrl: https://smsemarsys.accounts.ondemand.com/oauth2/token
          scopes: {}
x-sap-shortText: Process Partner service callbacks for the Emarsys SMS Partner API. Expected callbacks contain outbound message delivery reports and inbound messages.