Riverside Recordings API
Recording management and retrieval
Riverside Recordings API is one of 4 APIs that Riverside publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Recordings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and 1 JSON Schema.
This API exposes 5 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version v3.
Requests are made against a single base URL, https://platform.riverside.fm.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Riverside Recordings API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (ApiKeyAuth).
ApiKeyAuth— API Key passed as Bearer token in Authorization header
Paths & Operations 5
Across 4 paths, the API surfaces 5 operations — 1 DELETE, 4 GET. Each is listed below with its method, path, parameters, and response codes.
Recording management and retrieval
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Recording (10 properties), RecordingList (5 properties), Track (4 properties), Transcription (3 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 Riverside 3
Other APIs Riverside publishes across the network.