Developer center

---

To create an MS3 Token with the ExpressPlay Admin you must provide the token with the Content ID, Content Key and Content URL. The Content ID and Content Key are both created when packaging content; the Content URL is the hosting location of the packaged content. MS3 tokens require a special Content ID, this takes the form of urn:marlin:kid:<value> with <value> being the same hexadecimal value used for the property value when packaging content. A full Content ID for MS3 Token generation would be: urn:marlin:kid:12341234123412341234123412341234

To create a token for a piece of media, paste the full Content ID as described above into the Content ID field, the Content Key into the Content Key field, and the Content URL into the URL field. See the working examples below.

For BB tokens, the required fields are a bit different. You don’t need the content URL, but you do need to include a rightsType parameter which can be BuyToOwn or Rental.

Note: In the case of HLS content, you use the ‘hls://’ protocol identifier in the contentURL parameter. For DASH and MP4, you use http or https as appropriate. In the case of the HLS example above you should get a token similar to the one below

---

Full API documentation can be found here. This guide demonstrates the MS3 Token Request API which requires your Test Authenticator, found at admin.expressplay.com, the content key used to encrypt the piece of content, the content’s property <value> used when packaging the content, and the content hosting location in URL form. This information is formatted into a RESTful POST or GET request similar to the one demonstrated below.

Note: The Test Authenticator is used as the customerAuthenticator value in the REST API as demonstrated below using the same parameters as the ExpressPlay Admin example for DASH.

Note: In the case of HLS content, you should use the ‘hls://’ protocol identifier in the contentURL parameter. For DASH and MP4, you use http or https as appropriate. In the case of the DASH example above you should get an MS3 token similar to the one shown below.

And for BB tokens the base url is a bit different, and the parameters are same as the above BB example with the addition of a required actionTokenType=1 parameter to indicate that this is for a BB license token.