Configure DRM protection

API v2 lets you configure DRM protection at two levels:

• Profile level: Define default DRM settings for VOD and livestreams.
• Content level: Apply a custom configuration to an individual VOD or livestream, overriding the default settings.

You can use the profile defaults for all protected content or customize the settings for specific content.

1. Check if DRM is enabled on your organization

Before configuring DRM, check whether the DRM feature is available for your Dailymotion organization.

Retrieve the can_use_drm field from the profile object.

Required scope: profile.read

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own.

curl --request GET \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}?fields=can_use_drm' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}'

{
  "profile_id": "x123abc",
  "can_use_drm": true
}

DRM is available if can_use_drm is true.

If the value is false, DRM cannot be configured on that profile. Reach out to your Dailymotion Success Manager or our Support team to add the feature to your plan.

2. Configure default DRM settings at profile level

Profile-level settings define the default DRM configuration for protected content.

VOD and livestreams have separate configurations. Both support license expiration and optional key rotation, but only VOD supports play_duration field.

2.1. Register your RSA public key

​First, generate an RSA key pair on your backend.

Keep the private key secure: it is used to sign playback JWTs and must never be shared with Dailymotion or exposed to the client. Only the public key needs to be registered.

Send a PATCH request to the profile endpoint.

Required scope: profile.manage

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own

curl --request PATCH \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}' \
     --header 'content-type: application/json' \
     --data '
{
  "drm_public_key": "-----BEGIN PUBLIC KEY-----\\nMIIBIj...\\n-----END PUBLIC KEY-----"
}
'

204 No Content

The public key must meet the following requirements:

• Be PEM-encoded.
• Be a valid public key.
• Not exceed 2,000 characters.

Verify the registered key: To check that the key was registered successfully, retrieve the drm_public_key field.

Required scope: profile.read

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own.

curl --request GET \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}?fields=drm_public_key' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}'

{
  "profile_id": "x123abc",
  "can_use_drm": true,
  "drm_public_key": "-----BEGIN PUBLIC KEY-----\nMIIBIj...\n-----END PUBLIC KEY-----"
}

To remove the registered public key, set drm_public_key to null.

2.2. Configure default DRM settings for VOD and livestreams

Use the following request to define separate default DRM settings for VOD and livestream content. DRM configuration objects are replaced as a whole. Always include all required fields when updating them.

Required scope: profile.manage

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}' \
     --header 'content-type: application/json' \
     --data '
{
  "vod_drm_configuration": {
    "protection_granularity": "per_video",
    "protected_media_type": "both",
    "play_duration": "PT2H",
    "relative_expiration": "PT48H",
    "enable_key_rotation": true,
    "key_rotation_period": "PT24H"
  },
  "live_drm_configuration": {
    "protection_granularity": "per_live",
    "protected_media_type": "both",
    "relative_expiration": "PT48H",
    "enable_key_rotation": true,
    "key_rotation_period": "PT24H"
  }
}
'

204 No Content

2.3. Optionally, enable DRM protection by default for new content

Defining profile-level DRM settings does not automatically protect newly created content.

To apply DRM protection automatically to new content, set its default visibility to drm_protected in the profile's content_defaults .

Required scope: profile.manage

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer ••••' \
     --header 'content-type: application/json' \
     --data '
{
    "content_defaults": {
      "visibility": "drm_protected"
    }
  }'

This setting applies to newly created content only. Existing content remains unchanged.

3. Configure DRM on a VOD or livestream

When creating or updating content, you can choose between:

• Default settings: use the DRM configuration defined at profile level.
• Custom settings: override the profile defaults for a specific VOD or livestream.

In both cases, the content must have visibility set to drm_protected.

3.1. Apply default DRM settings

To use the profile defaults, set the content visibility to drm_protected. Dailymotion will apply the corresponding vod_drm_configuration or live_drm_configuration.

Required scope: video.manage live.manage

For new content

// Replace {PROFILE_ID}, {ACCESS_TOKEN} and {VIDEO_URL} with your own.

curl --request POST \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}/videos' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}' \
     --header 'content-type: application/json' \
     --data '
{
  "title": "My new video",
  "visibility": "drm_protected",
  "is_for_kids": false,
  "source": {
    "file_url": "{VIDEO_URL}"
  }
}
'

// Replace {PROFILE_ID} and {ACCESS_TOKEN} with your own.

curl --request POST \
     --url 'https://api.dailymotion.com/v2/profiles/{PROFILE_ID}/livestreams' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer {ACCESS_TOKEN}' \
     --header 'content-type: application/json' \
     --data '
{
  "title": "My live",
  "visibility": "drm_protected",
  "is_for_kids": false
}
'

For existing content

// Replace {VIDEO_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
  --url 'https://api.dailymotion.com/v2/videos/{VIDEO_ID}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'Content-Type: application/json' \
  --data '{
    "visibility": "drm_protected"
  }'

// Replace {LIVESTREAM_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
  --url 'https://api.dailymotion.com/v2/livestreams/{LIVESTREAM_ID}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'Content-Type: application/json' \
  --data '{
    "visibility": "drm_protected"
  }'

3.2. Apply a custom DRM settings

To use different DRM settings for a specific VOD or livestream, provide a custom drm_configuration at content level.

Set drm_configuration_source to custom in the protection object.

Content-level custom configurations are currently supported through PATCH requests only.

Required scope: video.manage live.manage

// Replace {VIDEO_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
  --url 'https://api.dailymotion.com/v2/videos/{VIDEO_ID}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'Content-Type: application/json' \
  --data '{
    "drm_configuration": {
      "protection_granularity": "per_quality",
      "protected_media_type": "both",
      "play_duration": "PT4H",
      "relative_expiration": "PT24H",
      "enable_key_rotation": true,
      "key_rotation_period": "PT12H"
    },
    "protection": {
      "drm_configuration_source": "custom"
    }
  }'

// Replace {LIVESTREAM_ID} and {ACCESS_TOKEN} with your own.

curl --request PATCH \
  --url 'https://api.dailymotion.com/v2/livestreams/{LIVESTREAM_ID}' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'Content-Type: application/json' \
  --data '{
    "drm_configuration": {
      "protection_granularity": "per_live",
      "protected_media_type": "both",
      "relative_expiration": "PT24H",
      "enable_key_rotation": true,
      "key_rotation_period": "PT12H"
    },
    "protection": {
      "drm_configuration_source": "custom"
    }
  }'

Keep in mind:

• The custom configuration replaces the existing default configuration. Include all required fields.
• VOD and livestream configurations have different schemas: play_duration is supported for VOD only.

4. Read the DRM configuration

You can read the DRM settings applied to a VOD or livestream, whether they come from the profile defaults or a custom configuration.

DRM fields are not returned by default. Include them explicitly in the fields parameter.

Required scope: video.read live.Read

// Replace {VIDEO_ID} and {ACCESS_TOKEN} with your own.

curl --request GET \
  --url 'https://api.dailymotion.com/v2/videos/{VIDEO_ID}?fields=video_id,visibility,protection.drm_configuration' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'Accept: application/json'

// Replace {LIVESTREAM_ID} and {ACCESS_TOKEN} with your own.

curl --request GET \
  --url "https://api.dailymotion.com/v2/livestreams/{LIVESTREAM_ID}?fields=livestream_id,visibility,protection,drm_configuration" \
  --header "Authorization: Bearer {ACCESS_TOKEN}" \
  --header "Accept: application/json"

Understand the response:

The response indicates which configuration source is being used through protection.drm_configuration_source.

{
  "video_id": "xvideo123",
  "visibility": "drm_protected",
  "protection": {
    "drm_configuration_source": "channel"
  },
  "drm_configuration": null
}

{
  "video_id": "xvideo123",
  "visibility": "drm_protected",
  "protection": {
    "drm_configuration_source": "custom"
  },
  "drm_configuration": {
    "protection_granularity": "per_quality",
    "protected_media_type": "both",
    "play_duration": "PT4H",
    "relative_expiration": "PT24H",
    "enable_key_rotation": true,
    "key_rotation_period": "PT12H"
  }
}

5. DRM configuration fields reference

The following fields are available for DRM configuration. DRM-specific fields are optional and must be explicitly requested with the fields query parameter when reading resources.

Profile DRM fields

Content DRM fields

For custom content settings, set drm_configuration_source to custom and provide the complete drm_configuration object. Content-level drm_configuration is currently available through PATCH requests only.

VOD DRM configuration fields

The vod_drm_configuration and VOD drm_configuration objects use the following fields:

Example:

{
  "protection_granularity": "per_quality",
  "protected_media_type": "both",
  "play_duration": "PT2H",
  "relative_expiration": "PT48H",
  "enable_key_rotation": true,
  "key_rotation_period": "PT24H"
}

Livestream DRM configuration fields

The live_drm_configuration and livestream drm_configuration objects use the following fields:

Livestream configuration does not include play_duration.

Important behavior and limitations

Keep the following points in mind when working with DRM-protected content:

• Content visibility: A DRM-protected resource is returned with visibility=drm_protected only to authorized members of the organization that owns the profile. Other callers see its visibility as private.

• Listings: DRM-specific fields are not included in content listings. The drm_protected visibility is not a supported listing filter.

• Unavailable DRM fields: Requests for DRM-specific fields on a profile without DRM enabled can return 403. A 409 response from the upstream content configuration route is represented as drm_configuration: null.

• Configuration updates: DRM configuration objects are replaced as a whole. Always provide all required fields when updating a configuration.

• Playback implementation: Configuring DRM through the API does not replace the Dailymotion DRM playback flow. Your backend must sign a JWT, which you then pass to the Player through setDrmConfig(). The Player automatically requests the appropriate license.

  Dailymotion supports Widevine, FairPlay and PlayReady. For implementation details, including JWT generation, RSA signing, license authorization and Player configuration, see implement DRM with the Dailymotion Player.