Wowza Streaming Engine REST API

Developer Webinar

Wowza Streaming Engine™ media server software has a REST API (application programming interface) that you can use to configure, manage, and monitor the media server through HTTP requests. In this video you'll learn the benefits of using the REST API to develop your streaming solution, how to get started with the REST API documentation and ways to query the Wowza™ REST service (with some cURL examples).

Resources

Download the webinar slides, which include information on the REST API endpoints, code examples, and the benefits for service providers and developers.

Check out our support articles to find out more and get started using the Wowza Streaming Engine REST API.

Presenters

Jamie Sherry

Senior Product Manager
Server Technologies

Ryan Jespersen

Senior Manager, Product Marketing
Wowza Media Systems

Questions & Answers

Q: We didn't receive any information about the beta test. When will the beta test start? 

A: If you download the latest version of Wowza Streaming Engine (4.2) the license allows access to the REST API.

 

Q: Can we use REST API on a trial verison?

A: Yes, visit wowza.com/pricing/trial for a trial of Wowza Streaming Engine.

 

Q: Can you give an example? Is there a publicly available documentation of the REST API, or only inside the Wowza server?

A: Currently only published within the documentation server found here: wowza.com/forums/content.php?644-How-to-access-documentation-for-Wowza-Streaming-Engine-REST-API

 

Q: Do we still need to do develop HTTProvides or Modules or can everything be handled by the REST API now? 

A: For the most part, many elements are accessible via the Rest API. However, there is some functionality not exposed where an http provider / module would be required.

 

Q: Can you configure load balancing with the REST API? Does it launch other servers? How does it work for licencing?

A: You can define the module/server listener/vhost listeners to setup the load balancer.

 

Q: Can you get any data about the status (sizes) of the buffers which handle the inbound streams? I understand that there's a buffer which can grow to 8s in length, but can we monitor these for each stream?

A: You can get monitoring statistics for each stream. Endpoint: GET /v2/servers/{serverName}/vhosts/{vhostName}/applications/{appName}/instances/{instanceName}/incomingstreams/{streamName}/monitoring/current - this would give you bytes In / Out for that stream and the rate. That is the extend via REST API.