Wowza Video REST API lifecycle management

The Wowza Video service naturally evolves over time as we improve the streaming experience. As part of this evolution, we add new features as well as remove functionality that becomes outdated. Our goal is to provide a well-maintained REST API that delivers reliably. To do this, we actively manage the lifecycle of the Wowza Video REST API.

API lifecycle

Our API lifecycle begins at the Beta stage, and 5 versions of our REST API are available at any given time. To ensure a stable API and minimize disruption to your streaming solutions, we add new features and remove outdated functionality in the Beta version of the API.

Every 6 months, we test and finalize the Beta version and then move all existing API versions along to the next lifecycle stage. Beta moves to Current, Current to Supported 1, and so on. When an API reaches Discontinued, it is removed from production and no longer available.

We recommend that you migrate to the new Current version of the REST API as it becomes available. This ensures you're using the most up-to-date, stable version of the API. As a version cycles through the stages, it becomes increasingly outdated and when it reaches Deprecated, it may no longer function as expected because of our re-routing policy for deprecated versions.

While we strive to maintain backwards compatibility between versions of the API to simplify your migration, it's not always possible when we add significant new functionality or improve architectural features. Staying current with the REST API is an easier migration task than migrating from an API version several stages removed from the current version with more cumulative changes.

Tip: Use automation to alert you when you are no longer using the current version of the REST API. To learn more, see Manage API versions in your code.

To learn more about each stage of our API lifecycle, click See more

Lifecycle schedule

As we bring our development processes into alignment with our lifecycle management process, this table reflects actual delivery dates, anticipated delivery dates, and scheduled delivery dates. 

  • Actual delivery dates are in plain text. These are the dates we delivered in our previous API lifecycle management process. 
  • Anticipated delivery dates are bold. These are the dates that we plan on moving the API to the next stage.

* Dates are in MM/DD/YYYY format.

API Version Beta Current Supported 1 Supported 2 Deprecated Discontinued
1.6 5/27/2020 12/1/2020 10/15/2021 4/19/2022 9/29/2022 3/15/2023
1.7 12/1/2020 10/15/2021 4/19/2022 9/29/2022 3/15/2023 9/20/2023
1.8 10/15/2021 4/19/2022 9/29/2022 3/15/2023 9/20/2023 3/20/2024
1.9 4/19/2022 9/29/2022 3/15/2023 9/20/2023 3/20/2024 9/18/2024
1.10 9/29/2022 3/15/2023 9/20/2023 3/20/2024 9/18/2024 3/12/2025

Manage API versions in your code

We recommend that you use the current version of the API, always. Use the Query for version status endpoint to automate notification when there's a new current version of the REST API available, then plan and execute your migration to the new current version.

curl -X GET \

-H "Authorization: Bearer ${WV_JWT}" \


The sample response looks similar to this, but differs according to current version status. Because current and supported APIs are the only ones intended for production use, those are the only statuses returned in the response.

  "1.9": {
    "status": "current",
    "base_uri": "/api/v1.9"
    "1.8": {
        "status": "supported",
        "base_uri": "/api/v1.8"

Consult the Wowza Video REST API migration guide for information about changes between API version as you plan your migration to a new current version of the API. 

More resources