How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Riverside

Riverside Recordings API

Recording management and retrieval

Documentation Provider Profile APIs.io OpenAPI GitHub

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.2.0, at version v3.

Requests are made against a single base URL, https://platform.riverside.fm.

5 operations 4 paths 6 schemas 1 DELETE4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://platform.riverside.fm
Authentication
HTTP Bearer
Contact
Riverside Support
License
Proprietary
Resource Areas
1

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.

Recordings 5

Recording management and retrieval

GET
/api/v2/recordings
List All Recordings
listAllRecordings 5 params → 200401
GET
/api/v1/recordings/{recording_id}
Get Recording
getRecording 1 param → 200401404
DELETE
/api/v1/recordings/{recording_id}
Delete Recording
deleteRecording 1 param → 204401404
GET
/api/v1/recordings/{recording_id}/files/{file_id}/download
Download File
downloadFile 2 params → 200401404
GET
/api/v1/recordings/{recording_id}/transcription/download
Download Transcription File
downloadTranscriptionFile 2 params → 200401404

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), TrackFile (3 properties). Each schema is shown below with its type and property counts.

Transcription
object
3 properties
Recording
object
A recording session with tracks and metadata
10 properties
Track
object
An individual audio or video track within a recording
4 properties
TrackFile
object
3 properties
RecordingList
object
5 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

riverside-recordings-api-openapi.yml Raw ↑

Other APIs Riverside publishes across the network.

Riverside Exports API
AE Profile APIs.io
Riverside Productions API
AE Profile APIs.io
Riverside Webinars API
AE Profile APIs.io
#Recordings
← Back to R APIs
API Details
ID
riverside:riverside-recordings-api
Base URL
https://platform.riverside.fm
Docs
https://docs.riverside.fm/
Provider
Riverside
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=riverside-recordings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/riverside-recordings-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Riverside Recordings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.