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 SMS Partner Callbacks API

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.

SAP Emarsys SMS Partner Callbacks 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 SMS, Webhook, Delivery Reports, and Inbound Messages. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 0.0.1.

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

2 operations 2 paths 6 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.1
Base URL
https://api.emarsys.net/sms/partner/v1
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

SAP Emarsys SMS Partner Callbacks API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oAuthAuthorization) using the clientCredentials flow. By default, every request must be authenticated.

  • oAuthAuthorization — OAuth client credentials grant type authorization

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. They span 2 resource areas: Delivery Reports, inbound-messages. Each is listed below with its method, path, parameters, and response codes.

Delivery Reports 1
POST
/clients/{clientId}/deliveryReports
Delivery reports callback
sendDeliveryReports 1 param body → 2024004014034044295XX
inbound-messages 1
POST
/clients/{clientId}/inboundMessages
Inbound messages callback
sendInboundMessages 1 param body → 2024004014034044295XX

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are InboundMessageBatch (1 property), DeliveryReportBatch (1 property). Each schema is shown below with its type and property counts.

DeliveryReport
DeliveryReportSuccess
DeliveryReportError
DeliveryReportBatch
object
1 property 1 required
InboundMessage
InboundMessageBatch
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emarsys-sms-partner-callbacks-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 Reporting API
SAP Emarsys Email Templates API
Where this information came from

This is an independent, third-party profile of SAP Emarsys SMS Partner Callbacks 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.