Setting up an OTT session

A client application must set up a new OTT session before starting playback. After a session has been successfully set up, the device may begin playing the content.

Request

To set up a new OTT session, send an HTTP POST request to:

Headers

• nv-authorizations – the request authorisation token. It can either be an SSP content authorisation token or an SSP device authentication token.

Response

A successful response returns an HTTP 200 status. The response body contains:

• The heartbeat period, in seconds (that is, how often the application must send a keep-alive request)

• The SSP session token to be used in the next request

Example

{
  "heartBeat": 30,
  "sessionToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ2ZXIiOiIxLjAiLCJkZXZpY2VJZCI6IjViNTg2NTFkYTRhNWQ1MDAwMWZkMGI2MCIsInRlbmFudElkIjoibmFncmEiLCJleHAiOjI1MjQ2MDgwMDAsImFjY291bnRJZCI6ImFjY291bnRJZDEiLCJqdGkiOiI0ZTU3NTExNi02N2Y0LTQ0MjEtOGNjMC04Yzc3NjljNWE0ZmIiLCJ0eXAiOiJEZXZBdXRoTiJ9.sfgCwsBGWG87UCZHDfAa-WnpD8yVopOxds8qkO2GJXA"
}

See the API documentation below for the full list of return codes.

See also

For full details of this API, see Set up SSM session

.