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

Wowza recordings API

The recordings operations are deprecated in 2.0. Use the /videos endpoints instead. Operations related to recordings, which are created through the ``/live_streams`` or ``/transcoders`` resources. The Wowza Video service can create MP4 recordings of your live streams and transcoded output. Recordings can be downloaded and saved locally. They're based on the highest-bitrate output rendition that Wowza Video generates from your video source. See [About recordings](https://www.wowza.com/docs/record-live-streams-and-transcoders#aboutREC) to learn more.

Wowza recordings API is one of 48 APIs that Wowza publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Recordings. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, and a changelog.

This API exposes 4 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v2.0.

Requests are made against a single base URL, https://api.video.wowza.com/api/v2.0.

4 operations 3 paths 8 schemas 1 DELETE3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2.0
Base URL
https://api.video.wowza.com/api/v2.0
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wowza recordings API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (WV_JWT).

  • WV_JWT — Your Wowza-generated access token, also called a JSON web token (JWT). Send it as a bearer token in the Authentication header of your requests. See [Authentica…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 3 GET. Each is listed below with its method, path, parameters, and response codes.

recordings 4

The recordings operations are deprecated in 2.0. Use the /videos endpoints instead. Operations related to recordings, which are created through the /livestreams or /transcoders re…

GET
/recordings
Fetch all recordings
listRecordings 3 params → 200401
GET
/recordings/{id}
Fetch a recording
showRecording 1 param → 200401403404410
DELETE
/recordings/{id}
Delete a recording
deleteRecording 1 param → 204401403404410422
GET
/recordings/{id}/state
Fetch the state of a recording
showRecordingState 1 param → 200401403404410

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are recording (15 properties), index_recordings (9 properties), recordings (1 property), Error422 (1 property). Each schema is shown below with its type and property counts.

Error404
object
1 property 1 required
Error403
object
1 property 1 required
recording
object
15 properties
Error422
object
1 property 1 required
index_recordings
object
9 properties
recordings
object
1 property 1 required
Error410
object
1 property 1 required
Error401
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wowza-recordings-api-openapi.yml Raw ↑

Other APIs Wowza publishes across the network.

Wowza Streaming Engine Java API
Wowza Flowplayer
Wowza GoCoder SDK
Wowza Real-Time Streaming SDK
Wowza advanced_token_authentication API
Wowza analytics_engagement API
Wowza analytics_ingest API
Wowza analytics_popularity API
Wowza analytics_viewers API
Wowza Applications API
Wowza assets API
Wowza categories API
Where this information came from

This is an independent, third-party profile of Wowza 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.