Adobe Experience Cloud Transactional Messages API
Operations for sending real-time transactional messages
Adobe Experience Cloud Transactional Messages API is one of 36 APIs that Adobe Experience Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Transactional Messages. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.
Requests are made against a single base URL, https://analytics.adobe.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Adobe Experience Cloud Transactional Messages API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
An API key is passed in the header as x-api-key (apiKey).
By default, every request must be authenticated.
bearerAuth— OAuth 2.0 access token obtained via Adobe I/O.apiKey— Adobe I/O client API key.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Operations for sending real-time transactional messages
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TransactionalMessageResponse (4 properties), TransactionalMessageRequest (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Adobe Experience Cloud 12
Other APIs Adobe Experience Cloud publishes across the network.