Skip to content
Wowza Video
/
/
/
Fetch viewer analytics da...

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.
Download OpenAPI description
openapi.json
openapi.yaml
Overview
License
Terms of Use
Languages
Servers
Mock server
https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi
https://api.video.wowza.com/api/v2.0

Live Streams

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.

Operations

Transcoders

Operations related to transcoders, output renditions, and output stream targets.

Operations

Stream Sources

Operations related to stream sources. You can create a Wowza stream source and associate it to a live stream or transcoder.

Operations

Stream Targets

Operations related to stream targets. A stream target is a destination for a stream. Stream targets can be Wowza Video edge resources; custom, external destinations, target destinations.

Operations

Schedules

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.

Operations

Real-Time Streams

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

Videos

Operations related to uploading and categorizing videos.

Operations

Categories

Operations related to categorizing videos.

Operations

Advanced Token Authentication

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".

Operations

Clipping

Operations related to clipping and stitching videos and live streams.

Operations

Viewers

Operations related to viewer analytics.

Operations

Fetch viewer analytics data for a VOD stream

Request

(Available from version 1.11) This operation returns the live and historic viewer data for a specific VOD stream. You'll use the query parameters to return live vs historic data, as well as specific types of viewer data.

Querying live data

  1. To get data for currently live streams, do not send from and to values.
  2. Use the include query parameter to specify what data you want to return, including: countries, renditions, devices, and trend data.

If you don't send any query parameters (to, from, or include), the total number of viewers is returned.

Querying historic data

  1. To get data for streams that ran previously, send from and to values.
  2. Use the include query parameter to specify what data you want to return, including: countries, renditions, devices, and trend data.

If you don't send include values, the total number of viewers is returned.

If the time range between from and to query parameters is:

  • Less than 60 minutes, the cache time between responses is 10 seconds.
  • More than 60 minutes, the cache time between responses is 60 seconds.
Path
idstringrequired

The unique alphanumeric string that identifies the VOD stream.

Query
fromstring(date-time)

Use this parameter, along with to, to return historic viewer data.

The start of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the from query parameter without setting the to query parameter, the data returned will reflect 30 days starting at the from date, or data up to to the current day, whichever is shorter.

Example: 2024-03-14T10:31:54.486Z

tostring(date-time)

Use this parameter, along with from, to return historic viewer data.

The end of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the to query parameter without setting the from query parameter, the data returned will be from the past 30 days or from your last invoice date, whichever is shorter.

Example: 2024-04-13T10:31:54.486Z

includestring

Specify the data you want returned in the response. You can send a comma-separated list of values.

Valid values are: countries, renditions, devices, and trend.

Example: countries,trend

time_zonestring

Specify the time zone you want the returned data to reflect.

Click to expand for the full list of valid values
LocationsWowza Video time_zone value
International Date Line WestEtc/GMT+12
Midway IslandPacific/Midway
American SamoaPacific/Pago_Pago
HawaiiPacific/Honolulu
AlaskaAmerica/Juneau
Pacific Time (US & Canada)America/Los_Angeles
TijuanaAmerica/Tijuana
Mountain Time (US & Canada)America/Denver
ArizonaAmerica/Phoenix
ChihuahuaAmerica/Chihuahua
MazatlanAmerica/Mazatlan
Central Time (US & Canada)America/Chicago
SaskatchewanAmerica/Regina
GuadalajaraAmerica/Mexico_City
Mexico CityAmerica/Mexico_City
MonterreyAmerica/Monterrey
Central AmericaAmerica/Guatemala
Eastern Time (US & Canada)America/New_York
Indiana (East)America/Indiana/Indianapolis
BogotaAmerica/Bogota
LimaAmerica/Lima
QuitoAmerica/Lima
Atlantic Time (Canada)America/Halifax
CaracasAmerica/Caracas
La PazAmerica/La_Paz
SantiagoAmerica/Santiago
NewfoundlandAmerica/St_Johns
BrasiliaAmerica/Sao_Paulo
Buenos AiresAmerica/Argentina/Buenos_Aires
MontevideoAmerica/Montevideo
GeorgetownAmerica/Guyana
Puerto RicoAmerica/Puerto_Rico
GreenlandAmerica/Godthab
Mid-AtlanticAtlantic/South_Georgia
AzoresAtlantic/Azores
Cape Verde Is.Atlantic/Cape_Verde
DublinEurope/Dublin
EdinburghEurope/London
LisbonEurope/Lisbon
LondonEurope/London
CasablancaAfrica/Casablanca
MonroviaAfrica/Monrovia
UTCEtc/UTC
BelgradeEurope/Belgrade
BratislavaEurope/Bratislava
BudapestEurope/Budapest
LjubljanaEurope/Ljubljana
PragueEurope/Prague
SarajevoEurope/Sarajevo
SkopjeEurope/Skopje
WarsawEurope/Warsaw
ZagrebEurope/Zagreb
BrusselsEurope/Brussels
CopenhagenEurope/Copenhagen
MadridEurope/Madrid
ParisEurope/Paris
AmsterdamEurope/Amsterdam
BerlinEurope/Berlin
BernEurope/Zurich
ZurichEurope/Zurich
RomeEurope/Rome
StockholmEurope/Stockholm
ViennaEurope/Vienna
West Central AfricaAfrica/Algiers
BucharestEurope/Bucharest
CairoAfrica/Cairo
HelsinkiEurope/Helsinki
KyivEurope/Kiev
RigaEurope/Riga
SofiaEurope/Sofia
TallinnEurope/Tallinn
VilniusEurope/Vilnius
AthensEurope/Athens
IstanbulEurope/Istanbul
MinskEurope/Minsk
JerusalemAsia/Jerusalem
HarareAfrica/Harare
PretoriaAfrica/Johannesburg
KaliningradEurope/Kaliningrad
MoscowEurope/Moscow
St. PetersburgEurope/Moscow
VolgogradEurope/Volgograd
SamaraEurope/Samara
KuwaitAsia/Kuwait
RiyadhAsia/Riyadh
NairobiAfrica/Nairobi
BaghdadAsia/Baghdad
TehranAsia/Tehran
Abu DhabiAsia/Muscat
MuscatAsia/Muscat
BakuAsia/Baku
TbilisiAsia/Tbilisi
YerevanAsia/Yerevan
KabulAsia/Kabul
EkaterinburgAsia/Yekaterinburg
IslamabadAsia/Karachi
KarachiAsia/Karachi
TashkentAsia/Tashkent
ChennaiAsia/Kolkata
KolkataAsia/Kolkata
MumbaiAsia/Kolkata
New DelhiAsia/Kolkata
KathmanduAsia/Kathmandu
AstanaAsia/Dhaka
DhakaAsia/Dhaka
Sri JayawardenepuraAsia/Colombo
AlmatyAsia/Almaty
NovosibirskAsia/Novosibirsk
RangoonAsia/Rangoon
BangkokAsia/Bangkok
HanoiAsia/Bangkok
JakartaAsia/Jakarta
KrasnoyarskAsia/Krasnoyarsk
BeijingAsia/Shanghai
ChongqingAsia/Chongqing
Hong KongAsia/Hong_Kong
UrumqiAsia/Urumqi
Kuala LumpurAsia/Kuala_Lumpur
SingaporeAsia/Singapore
TaipeiAsia/Taipei
PerthAustralia/Perth
IrkutskAsia/Irkutsk
UlaanbaatarAsia/Ulaanbaatar
SeoulAsia/Seoul
OsakaAsia/Tokyo
SapporoAsia/Tokyo
TokyoAsia/Tokyo
YakutskAsia/Yakutsk
DarwinAustralia/Darwin
AdelaideAustralia/Adelaide
CanberraAustralia/Melbourne
MelbourneAustralia/Melbourne
SydneyAustralia/Sydney
BrisbaneAustralia/Brisbane
HobartAustralia/Hobart
VladivostokAsia/Vladivostok
GuamPacific/Guam
Port MoresbyPacific/Port_Moresby
MagadanAsia/Magadan
SrednekolymskAsia/Srednekolymsk
Solomon Is.Pacific/Guadalcanal
New CaledoniaPacific/Noumea
FijiPacific/Fiji
KamchatkaAsia/Kamchatka
Marshall Is.Pacific/Majuro
AucklandPacific/Auckland
WellingtonPacific/Auckland
Nuku'alofaPacific/Tongatapu
Tokelau Is.Pacific/Fakaofo
Chatham Is.Pacific/Chatham
SamoaPacific/Apia

Default: Etc/UTC

Example: America/New_York

curl -i -X GET \
  'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/analytics/viewers/vod_streams/{id}?from=2019-08-24T14%3A15%3A22Z&to=2019-08-24T14%3A15%3A22Z&include=string&time_zone=string'

Responses

Success

Bodyapplication/json
vod_streamobject(vod_stream)
Example: {"id":"tvctq36g","viewers":7,"countries":[{"code":"US","viewers":3},{"code":"DE","viewers":4}],"renditions":[{"name":720,"viewers":7}],"devices":[{"name":"Desktop","viewers":7}],"time_zone":"America/New_York","trend":[{"sampled_at":"2024-03-14T00:00:00Z","viewers":7},{"sampled_at":"2024-03-15T00:00:00Z","viewers":7},{"sampled_at":"2024-03-16T00:00:00Z","viewers":7},{"sampled_at":"2024-03-17T00:00:00Z","viewers":7}]}
Response
application/json
{
  "vod_stream": {
    "id": "tvctq36g",
    "viewers": 7,
    "countries": [ … ],
    "renditions": [ … ],
    "devices": [ … ],
    "time_zone": "America/New_York",
    "trend": [ … ]
  },
  "limits": {
    "from": "2024-03-14T10:31:54.000Z",
    "to": "2024-04-13T10:31:54.000Z"
  }
}

Fetch viewer analytics data for a stream target

Request

(Available from version 1.11) This operation returns the live and historic viewer data for a specific stream target. You'll use the query parameters to return live vs historic data, as well as specific types of viewer data.

Querying live data

  1. To get data for currently live streams, do not send from and to values.
  2. Use the include query parameter to specify what data you want to return, including: countries, renditions, devices, and trend data.

If you don't send any query parameters (to, from, or include), the total number of viewers is returned.

Querying historic data

  1. To get data for streams that ran previously, send from and to values.
  2. Use the include query parameter to specify what data you want to return, including: countries, renditions, devices, and trend data.

If you don't send include values, the total number of viewers is returned.

If the time range between from and to query parameters is:

  • Less than 60 minutes, the cache time between responses is 10 seconds.
  • More than 60 minutes, the cache time between responses is 60 seconds.
Path
idstringrequired

The unique alphanumeric string that identifies the stream target.

Query
fromstring(date-time)

Use this parameter, along with to, to return historic viewer data.

The start of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the from query parameter without setting the to query parameter, the data returned will reflect 30 days starting at the from date, or data up to to the current day, whichever is shorter.

Example: 2024-03-14T10:31:54.486Z

tostring(date-time)

Use this parameter, along with from, to return historic viewer data.

The end of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the to query parameter without setting the from query parameter, the data returned will be from the past 30 days or from your last invoice date, whichever is shorter.

Example: 2024-04-13T10:31:54.486Z

includestring

Specify the data you want returned in the response. You can send a comma-separated list of values.

Valid values are: countries, renditions, devices, and trend.

Example: countries,trend

time_zonestring

Specify the time zone you want the returned data to reflect.

Click to expand for the full list of valid values
LocationsWowza Video time_zone value
International Date Line WestEtc/GMT+12
Midway IslandPacific/Midway
American SamoaPacific/Pago_Pago
HawaiiPacific/Honolulu
AlaskaAmerica/Juneau
Pacific Time (US & Canada)America/Los_Angeles
TijuanaAmerica/Tijuana
Mountain Time (US & Canada)America/Denver
ArizonaAmerica/Phoenix
ChihuahuaAmerica/Chihuahua
MazatlanAmerica/Mazatlan
Central Time (US & Canada)America/Chicago
SaskatchewanAmerica/Regina
GuadalajaraAmerica/Mexico_City
Mexico CityAmerica/Mexico_City
MonterreyAmerica/Monterrey
Central AmericaAmerica/Guatemala
Eastern Time (US & Canada)America/New_York
Indiana (East)America/Indiana/Indianapolis
BogotaAmerica/Bogota
LimaAmerica/Lima
QuitoAmerica/Lima
Atlantic Time (Canada)America/Halifax
CaracasAmerica/Caracas
La PazAmerica/La_Paz
SantiagoAmerica/Santiago
NewfoundlandAmerica/St_Johns
BrasiliaAmerica/Sao_Paulo
Buenos AiresAmerica/Argentina/Buenos_Aires
MontevideoAmerica/Montevideo
GeorgetownAmerica/Guyana
Puerto RicoAmerica/Puerto_Rico
GreenlandAmerica/Godthab
Mid-AtlanticAtlantic/South_Georgia
AzoresAtlantic/Azores
Cape Verde Is.Atlantic/Cape_Verde
DublinEurope/Dublin
EdinburghEurope/London
LisbonEurope/Lisbon
LondonEurope/London
CasablancaAfrica/Casablanca
MonroviaAfrica/Monrovia
UTCEtc/UTC
BelgradeEurope/Belgrade
BratislavaEurope/Bratislava
BudapestEurope/Budapest
LjubljanaEurope/Ljubljana
PragueEurope/Prague
SarajevoEurope/Sarajevo
SkopjeEurope/Skopje
WarsawEurope/Warsaw
ZagrebEurope/Zagreb
BrusselsEurope/Brussels
CopenhagenEurope/Copenhagen
MadridEurope/Madrid
ParisEurope/Paris
AmsterdamEurope/Amsterdam
BerlinEurope/Berlin
BernEurope/Zurich
ZurichEurope/Zurich
RomeEurope/Rome
StockholmEurope/Stockholm
ViennaEurope/Vienna
West Central AfricaAfrica/Algiers
BucharestEurope/Bucharest
CairoAfrica/Cairo
HelsinkiEurope/Helsinki
KyivEurope/Kiev
RigaEurope/Riga
SofiaEurope/Sofia
TallinnEurope/Tallinn
VilniusEurope/Vilnius
AthensEurope/Athens
IstanbulEurope/Istanbul
MinskEurope/Minsk
JerusalemAsia/Jerusalem
HarareAfrica/Harare
PretoriaAfrica/Johannesburg
KaliningradEurope/Kaliningrad
MoscowEurope/Moscow
St. PetersburgEurope/Moscow
VolgogradEurope/Volgograd
SamaraEurope/Samara
KuwaitAsia/Kuwait
RiyadhAsia/Riyadh
NairobiAfrica/Nairobi
BaghdadAsia/Baghdad
TehranAsia/Tehran
Abu DhabiAsia/Muscat
MuscatAsia/Muscat
BakuAsia/Baku
TbilisiAsia/Tbilisi
YerevanAsia/Yerevan
KabulAsia/Kabul
EkaterinburgAsia/Yekaterinburg
IslamabadAsia/Karachi
KarachiAsia/Karachi
TashkentAsia/Tashkent
ChennaiAsia/Kolkata
KolkataAsia/Kolkata
MumbaiAsia/Kolkata
New DelhiAsia/Kolkata
KathmanduAsia/Kathmandu
AstanaAsia/Dhaka
DhakaAsia/Dhaka
Sri JayawardenepuraAsia/Colombo
AlmatyAsia/Almaty
NovosibirskAsia/Novosibirsk
RangoonAsia/Rangoon
BangkokAsia/Bangkok
HanoiAsia/Bangkok
JakartaAsia/Jakarta
KrasnoyarskAsia/Krasnoyarsk
BeijingAsia/Shanghai
ChongqingAsia/Chongqing
Hong KongAsia/Hong_Kong
UrumqiAsia/Urumqi
Kuala LumpurAsia/Kuala_Lumpur
SingaporeAsia/Singapore
TaipeiAsia/Taipei
PerthAustralia/Perth
IrkutskAsia/Irkutsk
UlaanbaatarAsia/Ulaanbaatar
SeoulAsia/Seoul
OsakaAsia/Tokyo
SapporoAsia/Tokyo
TokyoAsia/Tokyo
YakutskAsia/Yakutsk
DarwinAustralia/Darwin
AdelaideAustralia/Adelaide
CanberraAustralia/Melbourne
MelbourneAustralia/Melbourne
SydneyAustralia/Sydney
BrisbaneAustralia/Brisbane
HobartAustralia/Hobart
VladivostokAsia/Vladivostok
GuamPacific/Guam
Port MoresbyPacific/Port_Moresby
MagadanAsia/Magadan
SrednekolymskAsia/Srednekolymsk
Solomon Is.Pacific/Guadalcanal
New CaledoniaPacific/Noumea
FijiPacific/Fiji
KamchatkaAsia/Kamchatka
Marshall Is.Pacific/Majuro
AucklandPacific/Auckland
WellingtonPacific/Auckland
Nuku'alofaPacific/Tongatapu
Tokelau Is.Pacific/Fakaofo
Chatham Is.Pacific/Chatham
SamoaPacific/Apia

Default: Etc/UTC

Example: America/New_York

curl -i -X GET \
  'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/analytics/viewers/stream_targets/{id}?from=2019-08-24T14%3A15%3A22Z&to=2019-08-24T14%3A15%3A22Z&include=string&time_zone=string'

Responses

Success

Bodyapplication/json
stream_targetobject(stream_target)
Example: {"id":"tvctq36g","viewers":7,"countries":[{"code":"US","viewers":4},{"code":"DE","viewers":3}],"renditions":[{"name":720,"viewers":7}],"devices":[{"name":"Desktop","viewers":7}],"time_zone":"America/New_York","trend":[{"sampled_at":"2024-03-14T00:00:00Z","viewers":7},{"sampled_at":"2024-03-15T00:00:00Z","viewers":7},{"sampled_at":"2024-03-16T00:00:00Z","viewers":7},{"sampled_at":"2024-03-17T00:00:00Z","viewers":7}]}
Response
application/json
{
  "stream_target": {
    "id": "tvctq36g",
    "viewers": 7,
    "countries": [ … ],
    "renditions": [ … ],
    "devices": [ … ],
    "time_zone": "America/New_York",
    "trend": [ … ]
  },
  "limits": {
    "from": "2024-03-14T10:31:54.000Z",
    "to": "2024-04-13T10:31:54.000Z"
  }
}

Fetch viewer analytics data for the most viewed live streams

Request

(Available from version 1.11) This operation returns viewer data for the top 100 live streams in an account.

Querying data

To get viewer data for the top 100 streams that ran previously, send from and to values.

If you do not send from and to values, the last five minutes' worth of live stream viewer data is returned.

If the time range between from and to query parameters is:

  • Less than 60 minutes, the cache time between responses is 10 seconds.
  • More than 60 minutes, the cache time between responses is 60 seconds.
Query
fromstring(date-time)

Use this parameter, along with to, to return historic viewer data.

The start of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the from query parameter without setting the to query parameter, the data returned will reflect 30 days starting at the from date, or data up to to the current day, whichever is shorter.

Example: 2023-01-14T10:31:54.486Z

tostring(date-time)

Use this parameter, along with from, to return historic viewer data.

The end of the range of time you want to view. Specify YYYY-DD-MMT HH:MM:SSZ where HH is a 24-hour clock in UTC. The range queried is rounded to the nearest second. If you set the to query parameter without setting the from query parameter, the data returned will be from the past 30 days or from your last invoice date, whichever is shorter.

Example: 2023-02-14T10:31:54.486Z

curl -i -X GET \
  'https://developer-m.wowza.com/_mock/docs/wowza-video/api/video/openapi/analytics/viewers/live_streams?from=2019-08-24T14%3A15%3A22Z&to=2019-08-24T14%3A15%3A22Z'

Responses

Success

Bodyapplication/json
live_streamsArray of objects(live_streams)required
Example: [{"id":"4Jjzstdt","viewers":3},{"id":"fFWxVsyj","viewers":4}]
live_streams[].​idstring(int32)

The unique alphanumeric string that identifies the live stream.

Example: "4Jjzstdt"
live_streams[].​viewersinteger(int32)

The total number of unique viewers to download at least one chunk of the stream. A unique viewer is a single IP address; multiple users that share the same IP address are counted once.

Example: 3
limitsobject

The time frame represented in the response.

Example: {"from":"2023-04-14T10:31:54.000Z","to":"2023-07-13T10:31:54.000Z"}
Response
application/json
{
  "live_streams": [
    { … },
    { … }
  ],
  "limits": {
    "from": "2023-04-14T10:31:54.000Z",
    "to": "2023-07-13T10:31:54.000Z"
  }
}

Ingest

Operations related to ingest analytics for a live stream.

Operations

Engagement

Operations related to engagement analytics for a VOD stream.

Operations

Popularity

Operations related to popularity analytics.

Operations

Quality of Experience

Operations related to quality of experience metrics.

Operations

Account

Operations related to stream analytics for an account.

Operations

Transcoders

Operations related to transcoder analytics.

Operations

Stream Targets

Operations related to stream target analytics, including CDN usage and viewer data.

Operations

Real Time Streams

Operations related to real-time streams analytics.

Operations

Assets

The assets operations are deprecated in 2.0. Use the /videos endpoints instead.

Operations related to assets, which are created through the /assets resources. The Wowza Video service can store and transcode mp4 files that you can tag, manage, and restream.

Operations

Players

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.

Operations

Recordings

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.

Operations

VOD Streams

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.

Operations

Storage

The storage operations are deprecated in 2.0.

Operations related to peak and current storage for an account.

Operations

VOD Streams (Usage)

The VOD stream operations are deprecated in 2.0.

Operations related to video on demand (VOD) stream analytics.

Operations