Manage your library with the Management API

📘

GOALS

After completing this article, you should be able to answer the following questions:
  • What is the Platform Management API?
  • What are the differences between v1 and v2?
  • When should I use v1 and v2?


If you are not a developer or prefer a simpler implementation, you can use one of JW Player's client libraries.


The Platform Management API enables you to manage all aspects of your library. If you need to create a player for a specific use case, upload content programmatically, or manage the security of your content, you can use the Platform Management API to complete these tasks.

This year, JW Player has begun developing Platform Management API v2 (v2). In addition to the capabilities of Platform Management API v1 (v1), v2 will include the following improvements:

  • API key management
  • Granular access control
  • RESTful API design practices
  • Ease of use

Choosing an API version

JW Player will gradually release v2 capabilities during the second half of 2020 into 2021. During this period, JW Player will maintain full support for both versions.

Use the following table to identify which capabilities are available within each version of the API. Be sure to check this table frequently to see what has been newly added to v2.

Feature areaPlatform Management API v1Platform Management API v2
Account management-
Player management-
Playlist management
Video management
Webhooks management-


Getting started

After deciding which version of the Platform Management API version addresses your needs, use the following articles to learn how to construct and execute API calls.

As an alternative, you can use one of the JW Player client libraries or plugins.


Updated a day ago



Manage your library with the Management API


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.