Operations related to live streams. A live stream is a single, linear video broadcast. You broadcast a live stream by receiving encoded source video into the Wowza Video service and letting Wowza Video transcode the stream and deliver it to viewers. A live stream is essentially a one-stop method for creating a transcoder, output renditions, stream targets, and associated players.
- Reference
- REST API
Wowza Video REST API Reference Documentation (v2.0)
API lifecycle phase: Current
| Want to take the API for a test run? All you'll need is a Wowza Video subscription, or free trial, for the API access token. Then, fork our collection in Postman and you'll be making calls to our REST API in minutes! See Trial the Wowza Video REST API using Postman for more information. |
This reference documentation provides details about the operations, parameters, and request and response schemas for every resource and endpoint in the Wowza Video REST API. Samples appear in the right column. Sample requests are presented in cURL (Shell) and JavaScript; some samples also include just the JSON object. Response samples are all JSON. Examples in cURL use environment variables so you can easily copy and paste them. To learn more, see Using cURL.
Reference documentation is available for every version of the API. Use the Version menu at the top of the page to access the reference doc for a different version of the API.
Note: If you haven't moved over to the new Wowza Video UI experience, you won't be able to access v2.0 of the API. We're migrating customers iteratively. See Upgrade to the Wowza Video 2.0 REST API for more information.
Operations related to schedules. Schedules allow you to automatically start or stop a live stream or transcoder at a predetermined date and time. You can configure a schedule to start and/or stop a live stream or transcoder just once, or you can configure it to repeat the behavior on a regular basis. See About schedules to learn more.
- Mock serverhttps://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}
- https://api.video.wowza.com/api/v2.0/schedules/{id}
- curl
- Java
- Python
- JavaScript
curl -i -X GET \
'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}'Success
The type of action that the schedule should trigger on the transcoder. The default is start.
The date and time that the schedule was created.
The month, day, and year that a recurring schedule should stop running. Specify YYYY-MM-DD.
A descriptive name for the schedule. Maximum 255 characters.
The day or days of the week that a recurring schedule should run.
A schedule can run one time only (once) or repeat (recur) until a specified end_repeat date. The default is once.
The month, day, and year that the recurring schedule should go into effect. Specify YYYY-MM-DD.
The month, day, year, and time of day that the action_type start should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
A schedule must be enabled to run. Specify enabled to run the schedule or disabled to turn off the schedule so that it doesn't run.
The month, day, year, and time of day that the action_type stop should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
The unique alphanumeric string that identifies the transcoder being scheduled.
{ "schedule": { "id": "28bwb5WT", "state": "disabled", "name": "Scheduled recurring start for my camera", "time_zone": "America/New_York", "transcoder_id": "VGB21JFJ", "transcoder_name": "My Camera", "recurrence_type": "recur", "recurrence_data": "monday,tuesday,wednesday,thursday,friday", "action_type": "start_stop", "start_transcoder": "2020-02-01T00:00:00.000Z", "stop_transcoder": "2020-02-29T23:59:59.999Z", "start_repeat": "2020-02-01T00:00:00.000Z", "end_repeat": "2020-02-29T00:00:00.000Z", "created_at": "2020-01-29T17:16:21.995Z", "updated_at": "2020-01-31T07:00:48.995Z" } }
Provide the details of the schedule to update in the body of the request.
The type of action that the schedule should trigger on the transcoder. The default is start.
Example: "action_type": "stop"
A descriptive name for the schedule. Maximum 255 characters.
Example: "name": "My Updated Schedule"
The month, day, and year that a recurring schedule should stop running. Specify YYYY-MM-DD.
Example: "end_repeat": "2020-02-29T00:00:00.000Z"
The day or days of the week that a recurring schedule should run.
Example: "recurrence_data": "monday,tuesday,wednesday,thursday,friday"
The month, day, and year that the recurring schedule should go into effect. Specify YYYY-MM-DD.
Example: "start_repeat": "2020-02-01T00:00:00.000Z"
The month, day, year, and time of day that the action_type start should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
Example: "start_transcoder": "2020-02-01T00:00:00.000Z"
The month, day, year, and time of day that the action_type stop should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
Example: "start_transcoder": "2020-02-29T23:59:59.999Z"
The time zone the schedule runs in.
Click to expand for the full list of valid values
| Locations | Wowza Video time_zone value |
|---|---|
| International Date Line West | Etc/GMT+12 |
| Midway Island | Pacific/Midway |
| American Samoa | Pacific/Pago_Pago |
| Hawaii | Pacific/Honolulu |
| Alaska | America/Juneau |
| Pacific Time (US & Canada) | America/Los_Angeles |
| Tijuana | America/Tijuana |
| Mountain Time (US & Canada) | America/Denver |
| Arizona | America/Phoenix |
| Chihuahua | America/Chihuahua |
| Mazatlan | America/Mazatlan |
| Central Time (US & Canada) | America/Chicago |
| Saskatchewan | America/Regina |
| Guadalajara | America/Mexico_City |
| Mexico City | America/Mexico_City |
| Monterrey | America/Monterrey |
| Central America | America/Guatemala |
| Eastern Time (US & Canada) | America/New_York |
| Indiana (East) | America/Indiana/Indianapolis |
| Bogota | America/Bogota |
| Lima | America/Lima |
| Quito | America/Lima |
| Atlantic Time (Canada) | America/Halifax |
| Caracas | America/Caracas |
| La Paz | America/La_Paz |
| Santiago | America/Santiago |
| Newfoundland | America/St_Johns |
| Brasilia | America/Sao_Paulo |
| Buenos Aires | America/Argentina/Buenos_Aires |
| Montevideo | America/Montevideo |
| Georgetown | America/Guyana |
| Puerto Rico | America/Puerto_Rico |
| Greenland | America/Godthab |
| Mid-Atlantic | Atlantic/South_Georgia |
| Azores | Atlantic/Azores |
| Cape Verde Is. | Atlantic/Cape_Verde |
| Dublin | Europe/Dublin |
| Edinburgh | Europe/London |
| Lisbon | Europe/Lisbon |
| London | Europe/London |
| Casablanca | Africa/Casablanca |
| Monrovia | Africa/Monrovia |
| UTC | Etc/UTC |
| Belgrade | Europe/Belgrade |
| Bratislava | Europe/Bratislava |
| Budapest | Europe/Budapest |
| Ljubljana | Europe/Ljubljana |
| Prague | Europe/Prague |
| Sarajevo | Europe/Sarajevo |
| Skopje | Europe/Skopje |
| Warsaw | Europe/Warsaw |
| Zagreb | Europe/Zagreb |
| Brussels | Europe/Brussels |
| Copenhagen | Europe/Copenhagen |
| Madrid | Europe/Madrid |
| Paris | Europe/Paris |
| Amsterdam | Europe/Amsterdam |
| Berlin | Europe/Berlin |
| Bern | Europe/Zurich |
| Zurich | Europe/Zurich |
| Rome | Europe/Rome |
| Stockholm | Europe/Stockholm |
| Vienna | Europe/Vienna |
| West Central Africa | Africa/Algiers |
| Bucharest | Europe/Bucharest |
| Cairo | Africa/Cairo |
| Helsinki | Europe/Helsinki |
| Kyiv | Europe/Kiev |
| Riga | Europe/Riga |
| Sofia | Europe/Sofia |
| Tallinn | Europe/Tallinn |
| Vilnius | Europe/Vilnius |
| Athens | Europe/Athens |
| Istanbul | Europe/Istanbul |
| Minsk | Europe/Minsk |
| Jerusalem | Asia/Jerusalem |
| Harare | Africa/Harare |
| Pretoria | Africa/Johannesburg |
| Kaliningrad | Europe/Kaliningrad |
| Moscow | Europe/Moscow |
| St. Petersburg | Europe/Moscow |
| Volgograd | Europe/Volgograd |
| Samara | Europe/Samara |
| Kuwait | Asia/Kuwait |
| Riyadh | Asia/Riyadh |
| Nairobi | Africa/Nairobi |
| Baghdad | Asia/Baghdad |
| Tehran | Asia/Tehran |
| Abu Dhabi | Asia/Muscat |
| Muscat | Asia/Muscat |
| Baku | Asia/Baku |
| Tbilisi | Asia/Tbilisi |
| Yerevan | Asia/Yerevan |
| Kabul | Asia/Kabul |
| Ekaterinburg | Asia/Yekaterinburg |
| Islamabad | Asia/Karachi |
| Karachi | Asia/Karachi |
| Tashkent | Asia/Tashkent |
| Chennai | Asia/Kolkata |
| Kolkata | Asia/Kolkata |
| Mumbai | Asia/Kolkata |
| New Delhi | Asia/Kolkata |
| Kathmandu | Asia/Kathmandu |
| Astana | Asia/Dhaka |
| Dhaka | Asia/Dhaka |
| Sri Jayawardenepura | Asia/Colombo |
| Almaty | Asia/Almaty |
| Novosibirsk | Asia/Novosibirsk |
| Rangoon | Asia/Rangoon |
| Bangkok | Asia/Bangkok |
| Hanoi | Asia/Bangkok |
| Jakarta | Asia/Jakarta |
| Krasnoyarsk | Asia/Krasnoyarsk |
| Beijing | Asia/Shanghai |
| Chongqing | Asia/Chongqing |
| Hong Kong | Asia/Hong_Kong |
| Urumqi | Asia/Urumqi |
| Kuala Lumpur | Asia/Kuala_Lumpur |
| Singapore | Asia/Singapore |
| Taipei | Asia/Taipei |
| Perth | Australia/Perth |
| Irkutsk | Asia/Irkutsk |
| Ulaanbaatar | Asia/Ulaanbaatar |
| Seoul | Asia/Seoul |
| Osaka | Asia/Tokyo |
| Sapporo | Asia/Tokyo |
| Tokyo | Asia/Tokyo |
| Yakutsk | Asia/Yakutsk |
| Darwin | Australia/Darwin |
| Adelaide | Australia/Adelaide |
| Canberra | Australia/Melbourne |
| Melbourne | Australia/Melbourne |
| Sydney | Australia/Sydney |
| Brisbane | Australia/Brisbane |
| Hobart | Australia/Hobart |
| Vladivostok | Asia/Vladivostok |
| Guam | Pacific/Guam |
| Port Moresby | Pacific/Port_Moresby |
| Magadan | Asia/Magadan |
| Srednekolymsk | Asia/Srednekolymsk |
| Solomon Is. | Pacific/Guadalcanal |
| New Caledonia | Pacific/Noumea |
| Fiji | Pacific/Fiji |
| Kamchatka | Asia/Kamchatka |
| Marshall Is. | Pacific/Majuro |
| Auckland | Pacific/Auckland |
| Wellington | Pacific/Auckland |
| Nuku'alofa | Pacific/Tongatapu |
| Tokelau Is. | Pacific/Fakaofo |
| Chatham Is. | Pacific/Chatham |
| Samoa | Pacific/Apia |
Default: Etc/UTC
Example: America/New_York
- Mock serverhttps://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}
- https://api.video.wowza.com/api/v2.0/schedules/{id}
- curl
- Java
- Python
- JavaScript
curl -i -X PATCH \
'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}' \
-H 'Content-Type: application/json' \
-d '{
"schedule": {
"action_type": "start_stop",
"name": "Scheduled start for my camera",
"end_repeat": "2020-02-29T00:00:00.000Z",
"recurrence_data": "monday,tuesday,wednesday,thursday,friday",
"start_repeat": "2020-02-01T00:00:00.000Z",
"start_transcoder": "2020-02-01T00:00:00.000Z",
"stop_transcoder": "2020-02-29T23:59:59.999Z",
"time_zone": "America/New_York"
}
}'Success
The type of action that the schedule should trigger on the transcoder. The default is start.
The date and time that the schedule was created.
The month, day, and year that a recurring schedule should stop running. Specify YYYY-MM-DD.
A descriptive name for the schedule. Maximum 255 characters.
The day or days of the week that a recurring schedule should run.
A schedule can run one time only (once) or repeat (recur) until a specified end_repeat date. The default is once.
The month, day, and year that the recurring schedule should go into effect. Specify YYYY-MM-DD.
The month, day, year, and time of day that the action_type start should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
A schedule must be enabled to run. Specify enabled to run the schedule or disabled to turn off the schedule so that it doesn't run.
The month, day, year, and time of day that the action_type stop should occur. Specify YYYY-MM-DD HH:MM:SS where HH is a 24-hour clock in UTC.
The unique alphanumeric string that identifies the transcoder being scheduled.
{ "schedule": { "id": "28bwb5WT", "state": "disabled", "name": "Scheduled recurring start for my camera", "time_zone": "America/New_York", "transcoder_id": "VGB21JFJ", "transcoder_name": "My Camera", "recurrence_type": "recur", "recurrence_data": "monday,tuesday,wednesday,thursday,friday", "action_type": "start_stop", "start_transcoder": "2020-02-01T00:00:00.000Z", "stop_transcoder": "2020-02-29T23:59:59.999Z", "start_repeat": "2020-02-01T00:00:00.000Z", "end_repeat": "2020-02-29T00:00:00.000Z", "created_at": "2020-01-29T17:16:21.995Z", "updated_at": "2020-01-31T07:00:48.995Z" } }
- Mock serverhttps://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}
- https://api.video.wowza.com/api/v2.0/schedules/{id}
- curl
- Java
- Python
- JavaScript
curl -i -X DELETE \
'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/schedules/{id}'Operations related to Real-Time Streaming at Scale. If your audience is fewer than 300 viewers or you want to deliver a stream in near real time alongside other delivery protocols, use our WebRTC solution.
To enable and purchase capacity for Real-Time Streaming at Scale for your account and access the /real_time operations, contact 720.279.8163 or schedule a call.
Operations related to using advanced token authentication, known in Wowza Video as a default playback token behavior option, with videos.
Use token authentication when distributing valuable or sensitive video content to audiences to ensure that only authorized users can access the content within the intended application. This allows for protection of intellectual property, compliance with regulations, and the ability to maintain control over content distribution. The token is embedded in the videos' embed URLs.
Through the UI or Wowza Video API, you can choose one of the following options for token authentication of a video:
NO_TOKEN - Video files are accessible and can be downloaded and played by anyone at any time. This is the default.
BASIC_TOKEN - The platform automatically creates tokenized video URLs. This setting makes it hard for a viewer to extract the video URL and store it for usage in unintended applications over time since the embed URL, which has the token as part of the URL, will only be playable for 48 hours. The token auto renews after 48 hours when used in the intended application.
ADVANCED_TOKEN - You add the stream's JS embed code (Share Stream) and a token to your site to provide tokenization. The protections are similar to those for the Basic Token option except you customize the time limit, geographical limits, etc. during token creation.
FOLLOW_DEFAULT: - The token behavior is based on the Default Playback Token Behavior setting you selected for your Wowza account. See the Org Settings page in Wowza Video article for where to set this configuration.
Note: You'll use the /videos endpoints to update and review the token authentication enums bulleted above.
Before selecting to use the ADVANCED_TOKEN, you must, first, either:
- Generate a key id via the Wowza Video API, then customize and generate a token via the Wowza Video 2.0 API to add to your site. You'll need the key id to create and sign the token.
- Generate a key id and key via the Wowza Video 2.0 API, then customize and generate a standard common access token (CAT) through the means you usually use to create tokens to add to your site. You'll need the key id and key to create and sign the token.
After you have your playback token, you add the video JS-embed and the playback token to your site if you're going to use the ADVANCED_TOKEN option. The JS-embed code automatically adds the player and related video to your site. See the section on <a href="how to embed the player and video".
The player operations are deprecated in 2.0. Create and update player configurations in the user interface. Any values you send using the player operations will be ignored.
Operations related to players, which are created through the /live_streams resource. Players created through Wowza Video live streams can be embedded into your own web page or played through a web page hosted by Wowza Video.
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 to learn more.
The VOD stream operations are deprecated in 2.0. Use the /videos endpoints instead.
Operations related to video on demand (VOD) streams, which are created through the /live_streams or /transcoders resources. A VOD stream is a recording of a live stream that viewers can replay at a later date. After the broadcast is over and the live stream or transcoder is stopped, Wowza Video creates the VOD stream and generates a playback URL. See About VOD Streams to learn more.