API Reference
StreamsPlaybackEncodingBitmovin Dashboard
Start typing to search…

Add SPEKE DRM key provider to a TS muxing

post
https://api.bitmovin.com/v1/encoding/encodings//muxings/ts//drm/speke
Path Params
string
required

Id of the encoding.

string
required

Id of the TS muxing

Body Params

The SPEKE DRM key provider to be created

string

Name of the resource. Can be freely chosen by the user.

string

Description of the resource. Can be freely chosen by the user.

string

User-specific meta data. This can hold anything.

outputs
array of objects
required
outputs*
string

Unique Identifier of the content, will be generated if not set

string

Optional key identifier, will be generated if not set.
For SPEKE DRM Configurations with the same contentId and kid the key provider
will provide the same keys.

string

16 byte initialization vector represented by a 32-character text string.
It is mandatory if systemIds contains AES128 or FairPlay.

provider
object
required

Key provider configuration for SPEKE

systemIds
array of strings
required
length ≥ 1

DRM system identifier of the content protection scheme. At minimum one is expected.
Not all systemIds are currently supported, support depends on the muxing type.

Relates to SPEKE implementation. See https://dashif.org/identifiers/content_protection/

systemIds*
Responses

Updated 2 months ago

Language
Credentials
Response 
Click Try It! to start a request and see the response here! Or choose an example:
application/json
Updated 2 months ago