Wowza Streaming Engine’s REST API lets you configure, manage, and monitor a server over HTTP. To use it, build a request URL from your server address and the API’s /v2/ resource path, choose the method documented for that resource, set the expected content headers, and authenticate using the server’s configured method. The default API address in Wowza’s examples uses port 8087; confirm your server’s configuration and the exact operation in the official REST API overview and OpenAPI reference.
Build the REST API request URL
Wowza documents this URL pattern: http://[your-wowza-server]:8087/v2/[path-to-resource]. Replace the bracketed values with the address of your Streaming Engine server and the route for the resource you want to manage. The port and route can differ if your deployment is configured differently.
For example, an application collection route follows this pattern: http://[your-wowza-server]:8087/v2/servers/{serverName}/vhosts/{vhostName}/applications. Use the actual server and virtual-host names for your installation; do not assume example names are universal. The public reference lists the route families and their supported operations.
Choose the endpoint, method, and content format
First identify the exact resource and operation in the OpenAPI reference. A method supported by one route is not necessarily supported by another.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- 【Technical parameter】H.265/H.264 Decoding; HDMI/CVBS/VGA Out，1XHDMI output, 1X VGA output, 1XCVBS output, 1X audio output, 1X Ethernet oupput
- 【MAX resolution】Support up to 4K (3840×2160@60hz/30hz) resolution output
- 【H.265 HDMI+CVBS+VGA 4K Decoder】The H.265 Decoder is high-definition decoder is a professional high-definition AV decoder.
- 【Multi-protocol Supporting】 Support HTTP, RTSP, RTMP, SRT, HLS(M3U8), UDP, RTP, Multicast, Unitcast, FLV etc streaming protocol decoding.
- 【Free Support and Service】Our products are backed with a 3-year limited warranty.Support remote technical service.You can contact our customer service by email
| Method | Typical purpose in Wowza’s overview |
|---|---|
GET |
Retrieve information |
POST |
Create records |
PUT |
Update information or perform actions on existing records |
DELETE |
Remove records |
Application routes illustrate why checking the reference matters: the collection supports GET and POST, while an individual application resource supports GET, POST, PUT, and DELETE; a separate PUT action route is also documented. These are route-specific capabilities, not a rule that every endpoint accepts all four methods.
Wowza’s examples use Accept and Content-Type headers to identify the response and request formats, commonly JSON, with UTF-8 character encoding. Set them to match the endpoint and payload; do not send a JSON body to a route expecting a different format.
Authenticate requests securely
A fresh Wowza Streaming Engine installation uses basic authentication by default, according to Wowza. Use credentials supported by the authentication configuration on your server. Keep authentication enabled in production: Wowza’s overview explicitly recommends against disabling it.
Basic authentication encodes the username and password with Base64, but Base64 is not encryption. Wowza says it is not considered secure unless used with HTTPS. Protect the connection with HTTPS where available and avoid sending credentials over an unencrypted network connection.
Recommended Free Tools
Authentication behavior depends on the configured method, password encoding, server version, and client. Wowza’s authentication guide lists basic, digest, digestfile, remotehttp, and none. Its compatibility details include:
basicsupports plaintext or bcrypt password encoding.digestanddigestfilesupport MD5 or SHA-256. Wowza recommends SHA-256 because of potential vulnerabilities with MD5, but its guide notes that in the documented digest configuration only Firefox supports SHA-256. That browser qualification is specific to the described setup; do not generalize it to every client or configuration.- Wowza Streaming Engine 4.8.8.01 and later allows digest or bcrypt hashes in
admin.password; version 4.8.19 and later supports SHA-256 encryption, according to the guide. remotehttpandnoneare listed without a password encoding. Remote HTTP authentication requires a remote authentication URL, shared secret, and identity inServer.xml; the remote endpoint must accept POST requests.
Disabling authentication with none also disables authentication for Wowza Streaming Manager and removes the ability to manage and configure the media server software using that manager. Do not use it as a shortcut for API access. Consult the authentication guide for the version and configuration you actually run.
Make a request with curl
Once you have the route, supported method, content format, and credentials, a curl request can be structured like this. Replace the placeholders and adapt the method and body to the selected operation:
curl -i -u 'username:password'
-H 'Accept: application/json; charset=utf-8'
-H 'Content-Type: application/json; charset=utf-8'
-X GET
'http://localhost:8087/v2/servers/{serverName}/vhosts/{vhostName}/applications'This example uses GET to request an application collection, following Wowza’s documented local-server pattern. Replace localhost if making the request from another machine, and supply the real server and virtual-host names. For a POST or PUT operation, use the body format and required fields shown for that endpoint in the reference; for DELETE, confirm the resource path before sending the request. Shell quoting and line-continuation syntax may need adjustment on Windows.
Find the endpoint and inspect the local API documentation
Use the public OpenAPI reference
The public OpenAPI reference identifies the REST API as version 2.0.0 and documents routes, methods, parameters, and responses. Use it to confirm the operation for the resource you need rather than inferring a route from another resource.
Use the local Swagger reference servlet and Postman
Wowza also documents a local Swagger/Postman discovery workflow for Wowza Streaming Engine 4.5.0 or later. After configuring and enabling the local documentation servlet and restarting the server, the guide retrieves http://localhost:8089/swagger.json. This documentation URL uses port 8089 in the described procedure; it is distinct from the REST API’s documented default port 8087. Follow the Postman guide for the servlet setup steps applicable to your installation.
Check server information when supported
The reference documents GET /restinfo for builds 15089 or later. It can return information including API version, server name, software version, REST build, and license validity. Check the build requirement before relying on this route.
Troubleshoot common request failures
- Connection refused or timeout: Confirm the server address, configured REST port, network reachability, and that the service is available. The documented examples use port 8087 for API requests, but a deployment may be configured differently.
- Authentication failure: Verify the username and password, configured authentication method, password encoding compatibility, and client support. Do not turn off authentication to bypass the error.
- Unsupported method or route: Check the exact resource path and supported method in the OpenAPI reference. Collection and individual-resource routes can expose different operations.
- Payload or content-type error: Match
Content-Typeto the request body andAcceptto the response format. Follow the endpoint’s schema and use UTF-8 encoding as in Wowza’s examples. - Local Swagger URL fails: The documented Postman flow requires Wowza Streaming Engine 4.5.0 or later, the local documentation servlet to be configured and enabled, and a server restart. Do not confuse its port 8089 URL with the REST API request port.
Or let it run in the cloud
Wowza Streaming Engine’s REST API is for administering Wowza Streaming Engine; it is not a service for keeping a pre-recorded YouTube stream running. If your separate goal is a 24/7 YouTube channel that loops uploaded videos, StreamNeo is a different option: upload a recording or playlist, add your YouTube stream key, and go live. It runs in the cloud, so nothing has to stay on at home; uploaded video streams at its original quality up to 4K 60fps at one flat price per slot, with automatic recovery if YouTube drops the stream. The first day is free with no card. Monthly pricing is $9.99 per month. See StreamNeo and its pricing, or start the free day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
