Getting started

Learn about the Management API and Delivery API.

📘

TIP

You can also manage your content, customize players, define advertising experiences, and more via your JW Player dashboard instead of integrating directly with our APIs.

When choosing how to integrate with JW Player's services, it is essential to select the correct API for your specific objective. Making this selection requires familiarization with JW Player's Platform APIs: Management API and Delivery API.

This chart visualizes the differences in use-cases between the Management API and the Delivery API.This chart visualizes the differences in use-cases between the Management API and the Delivery API.

This chart visualizes the differences in use-cases between the Management API and the Delivery API.

Use the Management API to integrate with your CMS

The Management API is a read-write API used to programmatically manage your library or connect to your CMS. This API requires authenticated calls and prevents the replay of previous requests. The Management API is optimized to be immediately consistent rather than capable of high volumes of requests.

For this reason, the Management API enforces a rate limit. When deciding which API to use, consider the volume of calls you will be making and whether or not the application strictly requires immediate consistency.

Use Case Examples

The Management API is most useful for implementations such as (but not limited to):

Use the Delivery API to build your sites and apps

​​The JW Platform Delivery API is read-only and considered eventually consistent because it is optimized for high delivery volume over data recency.​​The JW Platform Delivery API is read-only and considered eventually consistent because it is optimized for high delivery volume over data recency.

​​The JW Platform Delivery API is read-only and considered eventually consistent because it is optimized for high delivery volume over data recency.

The Delivery API is designed for high availability. It allows you to perform large volumes of requests. This API uses a CDN and short caching to optimize response time globally.

The content service packages your library into easily consumable templates, including RSS and JSON feeds, single-line player embeds, and adaptive bitrate streaming manifests. You can require that requests for your content are signed with expiring tokenized links.

Use Case Examples

The Delivery API is most useful for implementations such as (but not limited to):

👍

IMPORTANT

After using the Management API or JW Player dashboard to upload or update content, there may be up to 3 minutes of caching before the content's assets are available in the Delivery API.


Did this page help you?