Acquia Messages API
The Messages API from Acquia — 2 operation(s) for messages.
Acquia Messages API is one of 21 APIs that Acquia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include 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.0.0, at version 2.0.0.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Acquia Messages API declares
4 security schemes
for authenticating requests.
It supports OAuth 2.0 (Acquia_Cloud_API_Documentation_OAuth2) using the clientCredentials flow.
An API key is passed in the header as Authorization (Codebase_Service_JWT).
An API key is passed in the header as Authorization (MEO_Environment_Service_JWT).
An API key is passed in the header as Authorization (Site_Service_JWT).
Acquia_Cloud_API_Documentation_OAuth2— All Cloud API calls need to be authenticated in order to work. You authenticate using a token that you can generate on your Acquia Profile page. To generate a…Codebase_Service_JWT— Value for the Authorization header parameter.MEO_Environment_Service_JWT— Value for the Authorization header parameter.Site_Service_JWT— Value for the Authorization header parameter.
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.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Acquia_Cloud_API_Documentation_error (2 properties), Acquia_Cloud_API_Documentation_message (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 Acquia 12
Other APIs Acquia publishes across the network.