Adobe Campaign Workflow API
Start, stop, and signal workflows. PostEvent sends asynchronous signals to trigger workflow transitions.
Adobe Campaign Workflow API is one of 20 APIs that Adobe Campaign publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Workflow. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and an AsyncAPI specification.
This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 8.0.0.
Requests are made against a single base URL, https://{instance}.campaign.adobe.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Adobe Campaign Workflow API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as X-Security-Token (SessionToken).
SessionToken— Security token obtained from xtk:sessionLogon. Must be passed alongside the session token cookie (sessiontoken) on all authenticated requests. Tokens have a 24…
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.
Start, stop, and signal workflows. PostEvent sends asynchronous signals to trigger workflow transitions.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are SOAPFault (3 properties), WorkflowPostEventRequest (3 properties), WorkflowRequest (1 property). 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 Campaign 12
Other APIs Adobe Campaign publishes across the network.