Concept of Services

What is it that we call "Service" on


A service defines the URL that your end-user OTT clients must use to access your contextualized streaming services.

There is no global definition of services as they are defined differently for each application. You can find bellow a short description of each service and the links to the detailed section of each service.

TypeBased onAims at...
Ad insertionA live source or an Asset catalog & an ad serverInserting or replacing ads in live or VOD sources
Virtual channelA live source & optionnaly an Ad serverBuilding a live channel with different live, asset and ad contents
Content replacementA live source and a default replacement contentReplacing for some periods the live source with alternative VOD or live contents

The API to create, read, update or delete Services can be found here (link).

Service Format

You can define only one combination of streaming format per service (e.g. DASH or HLS).
This level of granularity is intended to provide the maximum level of flexibility and to allow you to apply different policies, rules or contextualization based upon individual combinations. Therefore, you need to define multiple Service variants if you have multiple combinations (e.g. packaging formats, packaging formats versions, DRM versions, etc.).

For the Content Replacement application, a suffix-based naming convention allows linking of multiple service variants with a common "Media ID" defined through the SCTE 224 API to simplify batch processing.
More details can be found in the Mapping of ESNI Media Id with service variants section.

Service Tags

There are three types of tags defined in the platform for your services.
They refer to your environment and can be used to help you sort services by usage or readiness.
Tags are optional, informative only and have no impact on how services are processed or charged.

TagTypical use case
LabQuick test and evaluation
StagingStaging/pre-production stage

Service URL endpoint and Media delivery's does not offer "yet" CDN delivery services, which means that the Service URL endpoint is only the Manifest endpoint, not the video fragments endpoint.

It is worth noting that for testing or demonstration purpose, streaming media segments from is allowed, but is not a valid configuration for Production. You may find that it is allowed if the original and alternate content (aka Replacement content) are hosted on the exact origin when no specific routing is necessary, or if the Ads are hosted by in the context of Ad Insertion Services.

Nevertheless, this does not fit production traffic and may not work in most cases.

We recommend visiting the Using with a CDN page to configure a CDN behind and enjoy efficient delivery.