Ably History API
The History API from Ably — 2 operation(s) for history.
Ably History API is one of 12 APIs that Ably publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.0.1, at version 1.0.32.
Requests are made against a single base URL, https://control.ably.net/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Ably History API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearer_auth).
bearer_auth— Control API uses bearer authentication. You need to generate an access token for use with this API. More details can be found in the Ably docs .
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Message (8 properties), PresenceMessage (8 properties), Error (5 properties), Notification (5 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 Ably 11
Other APIs Ably publishes across the network.