Publishing URL format

The following table describes the entrypoint hostnames and pathnames for Media Services Live 4.0 and above.

Encoders should be capable of using a POST URL in the following format.

Media Services Live 4.0 and above

Primary publishing hostname:


Backup publishing hostname:


URL path for HLS:




URL path for HDS, DASH, or CMAF:

http://p-ep{stream_id}<format>/<stream_id>/<uniquesourcename> /<sessionID>/<bitrateID>/<OPTIONAL_PATH>/ <somename>_<sequence#>.extension

URL path parameter descriptions
URL Path Element Description
format The ingest format HDS, DASH, or CMAF. You need not specify the format for HLS.
stream_id Unique identifier for the stream provided by Akamai.
uniquesourcename This is a nomenclature change of the current event name. This is the first URL path component following the stream_id. Customers will use this name to identify the current media source from a set of sources ingesting into Akamai.
sessionID This helps to distinguish different encoder restart points and ensure that path duplications do not overwrite the media objects across the restart points.

For example: for a 24x7 source, a good recommendation is to use a string with the date time string at the time of connection. <stream_id>/<uniquesourcename>/20160628T18h22m10s/* or <stream_id>/<uniquesourcename>/T1467082295/*

For details about the unique session ID, see Unique session ID

bitrateID A unique path element to distinguish media segments specific to a bitrate. It is mandatory to have this path element. Bitrate in kilo bits of the corresponding media object should be extractable using a regular expression such as: */rend4000K/*, */master_3000K/*, */bitrate3000K/*.
OPTIONAL_PATH Other fixed pathnames for specific work flows that are not mandatory. For software releases prior to Media Services Live 4.0, this is the directory rollover pathname.

Media Services Live 4.0 and above does not require directory rollover. You can upload all of the segment objects for a specific bitrate into the same URL path.

However, to ensure compatibility the encoder should continue to support both directory rollover as well as non-rollover options in the short term.

There are no changes on the delivery side. The playback URL format remains the same as previous MSL versions. For example, if the format is HLS it is:[stream_id]/[event_name]/[filename_.m3u8_or_.mpd]