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.2.0, at version v2.0.
Requests are made against a single base URL, https://api.video.wowza.com/api/v2.0.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Wowza transcoders 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 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.
This is an independent, third-party profile of Wowza transcoders 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.