Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

HLS Video/Playlist URL


I had a question about using HLS when combining both JW platform and player.

Because of technical/business limitations with our client, we are unable to use the platform embed code to create players in some places, and are instead creating them using the player JS API. We would like these to work the same as the players generated via embed codes. Looking at the source generated by the embed code, it appears that the player is created with a "playlist" option pointing to a URL, in the following format:<video_key>.xml

This URL returns a feed with all the necessary information/file URLs for HLS streaming. It seems like we could use this same playlist URL when generating our own players, but I didn't see it anywhere on the API reference, so I am unsure if that is a stable/safe API call to rely on.

Is this a solution that would work for us, or is there a better way to take advantage of JW platform's HLS streaming ability through manually created players?


4 Community Answers

Remco van Bree

JW Player Support Agent  
0 rated :

While this will work, this URL scheme is indeed not guaranteed to be stable. Also, loads on the jw6 feeds will not generate any analytics so your traffic will not show any relationship to the analytics in our dashboard if you do this. There is no official URL scheme for HLS streams either, also because loads on manifests will not generate any analytics either.


0 rated :

So is there another option that would work for us? Also, we don't currently use the analytics features, so it's not a dealbreaker if the solution doesn't generate any.


0 rated :

Any new on this?

We are also using the same urls,<video_key>.xml, A LOT.

The reason is that we load the player once and then change video/audio several times in the same player the the API method "load(url)".

all the best

Remco van Bree

JW Player Support Agent  
0 rated :

This has always worked this way. While the JW6 feeds are not officially documented and supported, they are fairly stable.

If, at some point, we were to retire the jw6/<video_key>.xml endpoint, we would first point our player at something else and then log traffic on the remaining endpoint for a week or so in order to identify all customers that would be using these feeds and notify them that they would need to update.

This question has received the maximum number of answers.