What's changed
This topic covers REST API changes that occurred between the release of v1.9 and v1.10. These changes fall into two categories:
- Changes present only in v1.10.
- Changes that originate from the development of v1.10, but also retroactively apply to earlier versions of the API. These are non-breaking changes unless otherwise communicated by Wowza.
Highlights:
-
Added the filtering parameter to the
GET /assets
endpoints. - Added functionality to create only an MP4 when you record a real-time stream.
Only in v1.10
Over the course of development, we made the following changes to the REST API from v1.9 to v1.10. These changes are present in v1.10 only.
Updated endpoints
While developing v1.10 of the API, we made changes to the following endpoints:
- Assets
- Live streams
- Players
- Real-time streams
Assets
-
Added the
filter
parameter to theGET /assets
endpoints. Previously, these endpoints only supported thequery
parameter.Examples
-
Filter
—
https://api.video.wowza.com/api/beta/assets?filter[0][field]=created_at&filter[0][gte]=2021-07-14T17:47:45.000Z
-
Query
—
https://api.video.wowza.com/api/beta/assets?sort_direction=desc&sort_column=created_at&per_page=30&state=completed&query=sample
-
Filter
—
See Get filtered query results with the Wowza Video REST API for more information.
-
Updated
DELETE /assets/{id}
to allow for deleting assets in the processing state. Previously, you could only delete an asset in the uploading, failed, or completed state. When an asset is deleted, any related recordings and VOD streams are removed.
Live Streams
We've changed the request and response format for configuring the hosted page and the player. This change groups the configuration options for each object together in a more structured way.
v1.9
|
v1.10 |
---|---|
|
|
Player
We've changed the request and response format for configuring the hosted page. This change groups the configuration options together in a more structured way.
v1.9
|
v1.10 |
---|---|
|
|
Real-time streams
This change impacts Wowza Video subscribers only. You're a Wowza Video subscriber if you have access to Asset Management and Historic and Live Analytics in the user interface.
When you record a real-time stream, an MP4 file and an HLS stream for
video-on-demand (VOD) replay are created. VOD streams can take a bit of
processing time as multiple renditions are created. If you only need the
MP4, you can save processing time by setting
disable_vod_encoder
to true
on POST /real_time
.
v1.9
|
v1.10 |
---|---|
|
|
In v1.10 and earlier versions
After the release of version 1.10 and during the development of version 1.10, we made the following changes to 1.10 that also retroactively change earlier versions of the API. You might already be aware of these changes as they've been released and the changes communicated through the Wowza Video REST API release notes, but you might still consider them as you upgrade to version 1.10.
Wowza Flowplayer is default player for new live streams
Change present in: v1.7 through v1.10
This change impacts Wowza Video subscribers only. You're a Wowza Video subscriber if you have access to Asset Management and Historic and Live Analytics in the user interface.
Wowza Flowplayer is the default player for new live streams. To support this, the following changes were made:
-
Added
wowza_flowplayer
as the default value totype
in theplayer
object for the following/live_streams
endpoints:-
POST /live_streams
-
GET /live_streams/{id}
-
PATCH /live_streams/{id}
-
-
Added
wowza_flowplayer<
as the default value totype
for the following/players
endpoints:-
GET /players
-
GET /players/{id}
-
PATCH /players/{id}
-
If you're a Wowza Video subscriber, you can update an existing live
stream's player to
wowza_flowplayer
,
but won't be able to change it later because Wowza Flowplayer is the
only option if you are a subscriber.
Removed regions from GET /real_time
Change present in: v1.9 through v1.10
Removed
Original
|
Updated |
---|---|
|
|
Changed the value of a video codec in /transcoders
Change present in: v1.7 through v1.10
A value for video_codec
returned in the following endpoints is changed from
avc1
to h264
:
-
GET /transcoders/{transcoder_id}/uptimes/{id}/metrics/current
-
GET /transcoders/{transcoder_id}/stats
Original
|
Updated |
---|---|
|
|