Wowza transcoders API
Operations related to transcoders, output renditions, and output stream targets. ### Transcoders Wowza Video transcoders allow you to customize transcoding processes by creating transcoders thatare optimized for various network or streaming conditions. When you create a transcoder through the ``/transcoders`` endpoint, you must manually configure output renditions and associated output stream targets. Transcoders, like live streams, can be adaptive bitrate or passthrough. An adaptive bitrate transcodergenerates multiple output renditions of your live stream, at different bitrates. A passthrough transcoder, in contrast, sends the source video to a stream target without performing transcoding. Passthrough transcoders, which can only be created if you have a subscription plan that supports them, accrue processing time, bandwidth, and egress usage, but much less than their adaptive bitrate counterparts. ### Output Renditions Before you can start an adaptive bitrate transcoder, you must use the ``/transcoders/{transcoder_id}/outputs``operations to define the adaptive bitrate output renditions that you want the transcoder to create. Passthrough transcoders require only one output rendition because they send source video to a stream target without transcoding. ### Output Stream Targets Transcoders require output stream targets before you can start them. Although you create and configurestream targets using the different ``/stream_targets`` operations, you must associate a stream target to a transcoder's output rendition using the /transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets operations. For an adaptive bitrate transcoder with multiple output renditions defined, you must create output stream targets to associate a stream target to each output rendition. For a passthrough transcoder, you only need one output stream target.
Wowza transcoders API is one of 48 APIs that Wowza publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include transcoders. 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 36 operations across 25 paths, and defines 31 schemas. It is described by OpenAPI 3.0.3, at version 2.0.0.
Requests are made against a single base URL, http://localhost:8087.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Wowza transcoders API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
It uses HTTP digest authentication (digestAuth).
By default, every request must be authenticated.
basicAuth— HTTP Basic Authentication using Wowza Streaming Engine admin credentialsdigestAuth— HTTP Digest Authentication
Paths & Operations 36
Across 25 paths, the API surfaces 36 operations — 4 DELETE, 15 GET, 3 PATCH, 4 POST, 10 PUT. Each is listed below with its method, path, parameters, and response codes.
Operations related to transcoders, output renditions, and output stream targets. Transcoders Wowza Video transcoders allow you to customize transcoding processes by creating trans…
Schemas 31
The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are transcoder (38 properties), output (18 properties), schedule (15 properties), index_recordings (9 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 Wowza 12
Other APIs Wowza publishes across the network.