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 Service API

Published by SAP Emarsys as OpenAPI 3.0.3 with 5 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. The servers[] host api.sms-partner.io is the reference base for the PARTNER-hosted implementation; SAP Emarsys authors and owns the contract (info.title "SAP Emarsys SMS Partner Service", contact team-sms@emarsys.com).

SAP Emarsys SMS Partner Service 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, Partner Integration, and Messaging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

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

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

5 operations 3 paths 17 schemas 1 DELETE1 GET2 POST1 PUT

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.sms-partner.io/sms/partner/v1
Authentication
OAuth 2.0
Resource Areas
3

Authentication & Security 1

SAP Emarsys SMS Partner Service 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 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 1 GET, 2 POST, 1 PUT. They span 3 resource areas: Client Configuration, Client Configuration Test, Outbound Message Sending. Each is listed below with its method, path, parameters, and response codes.

Client Configuration 3
PUT
/clients/{clientId}/configuration
Create or update a single client's configuration
createOrUpdateClientConfiguration 1 param body → 2004004014035XX
GET
/clients/{clientId}/configuration
Get a client's configuration by their ID
getClientConfiguration 1 param → 2004034045XX
DELETE
/clients/{clientId}/configuration
Delete a client's configuration by their ID
deleteClientConfiguration 1 param → 2044034045XX
Client Configuration Test 1
POST
/testConnection
Test connection with the provided custom fields with the provider
testConnection body → 2004004014035XX
Outbound Message Sending 1
POST
/clients/{clientId}/messages
Send SMS messages to the Partner API
sendMessages 1 param body → 2024004014034044295XX

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are OutboundMessageError (3 properties), TestConnectionFailureResponse (3 properties), InvalidFieldError (3 properties), GetClientConfigurationResponse (2 properties). Each schema is shown below with its type and property counts.

CustomFieldValues
object
Object containing the values the client entered during onboarding mapped by their custom field name as key.
CallbackUrl
object
1 property 1 required
ClientCallbackUrls
object
2 properties
GetClientConfigurationResponse
object
2 properties 2 required
CreateOrUpdateClientConfigurationResponse
object
1 property 1 required
CreateOrUpdateClientConfigurationRequest
object
1 property 1 required
TestConnectionRequest
object
1 property 1 required
TestConnectionSuccessResponse
object
1 property 1 required
TestConnectionFailureResponse
object
3 properties 3 required
InvalidFieldError
object
3 properties 3 required
InvalidFieldErrors
object
1 property
OutboundMessage
OutboundMessageBatch
object
1 property 1 required
OutboundMessageError
object
3 properties 2 required
OutboundMessageBatchGlobalError
object
1 property
OutboundMessageBatchMessageSpecificError
object
1 property
OutboundMessageBatchError

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emarsys-sms-partner-service-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 Service 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.