Assigning DRM Policies

Once configured, you can assign a DRM policy at the account or asset level.

An Ooyala Customer Success Manager or Support Engineer must set up your policies before you can assign them to assets.

To assign a DRM policy to an asset:

  1. Get the ID for the DRM policy.
    [GET]/v2/drm_policies

    Backlot returns a response similar to the following.

    {  
       "items":[  
          86ff97ae7c81495eacbd9a01feff0f21,
          43ff97ae7c81495eacbd9a01feee0f38
       ]
    }
    Note:

    Try out the code samples using your account credentials in the Ooyala Scratchpad. For information about using the Scratchpad, see Practice Making Requests with the Scratchpad. To launch the scratchpad, go to Ooyala API Scratchpad.

  2. Assign the DRM policy to an asset.
    [PUT] /v2/assets/IzNnllMjphu2XF3_UgPROoCi9B2rtWs/drm_policy/86ff97ae7c81495eacbd9a01feff0f21

    Backlot returns a 200 response.

    Note:

    Try out the code samples using your account credentials in the Ooyala Scratchpad. For information about using the Scratchpad, see Practice Making Requests with the Scratchpad. To launch the scratchpad, go to Ooyala API Scratchpad.

  3. If you want to make a DRM policy the default for your account, you can assign the policy at the account level.
    [PUT] /v2/provider_drm_policy/86ff97ae7c81495eacbd9a01feff0f21

    Backlot returns a 200 response.

    Note:

    Try out the code samples using your account credentials in the Ooyala Scratchpad. For information about using the Scratchpad, see Practice Making Requests with the Scratchpad. To launch the scratchpad, go to Ooyala API Scratchpad.

Was this article helpful?