Stream URL
The stream’s URL has the following structure (not all elements are always required):
<transport>://<host>:<port>/<mount>[<mountSuffix>]?[lsid=<Listener ID>][&pageURL=<URL>][&sbmid=<SBMID>][&burst-time=<seconds>|&burst-time-ms=<milliseconds>][&tdtok=<token>][&<targeting-attribute>=<targeting-value>...]
The <transport>, <host>, <port>, and <mount> values are from the Provisioning Response. Their proper use is detailed in Connection Management.
For information on Targeting Attributes, see Advertising Technical Specification.|&
Stream URL Query Parameters
| Parameter | Description |
|---|---|
lsid | Listener ID. See Listener ID Management. (Note that the uuid listener ID parameter has been deprecated; use lsid.) |
pageURL | When a mount is configured with referrer checking, and the player is not a Web browser, the player must provide a referrer URL that is valid for the requested stream. |
sbmid | Sideband Metadata Session ID. See Sideband Metadata. |
burst-time | Burst size, in seconds, for the playback buffer. This parameter is ignored if burst-time-ms is specified. See Playback Buffer. |
| burst-time-ms | Burst size, in milliseconds, for the playback buffer. See Playback Buffer. |
autoplay | Flag that indicates if the session has been initiated from a player auto-play. Possible values are autoplay=0 (not initiated via auto-play) and autoplay=1 (initiated via auto-play). Auto-play of audio content is strongly discouraged since in some cases, auto-played streams are not audible as the volume may be muted while the stream continues to be active. Triton Digital recommends that any initiation of audio content playback is determined by an overt user gesture, such as a tap or a click. |
tdtok | Access token. Required to grant stream access privileges. See Access Token, below. |
Other parameters | A range of targeting attributes can be sent by the player as query parameters. |
Access Token
Also see: Partner Token.
This is a Triton Digital secure token (tdtok) that can grant various privileges to any player (either a web player or an app) that provides the token when accessing the content.
For example, you can restrict access to specific content (e.g., high bitrate stream) to registered listeners only. Alternatively, you can deliver fewer ads or even advertising-free content to authorized players or registered listeners who are logged in. Non-logged in listeners, or listeners who connect via an aggregator or other third-party method, will receive the content with more stitched-in ads.
The format of the access token is documented in Secure Token Specification. You will need a private key to sign the token; a unique key is assigned to each publisher or partner. Also, access tokens must be enabled on your stations within their programming schemes, which are developed and maintained by Triton Digital. Please reach out to Triton Digital Customer Support to get your private key and to enable your stations for access tokens.
Using the example from Secure Token Specification, the resulting parameter would be:
tdtok=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiIsImtpZCI6ImExYjJjM2Q0ZTUifQ.eyJpc3MiOiJwZHZ5Iiwic3ViIjoiZm9vQGJhci5jb20iLCJpYXQiOjE0Mjk4MDI3MTYsInRkLXJlZyI6dHJ1ZX0.YeNcfr7Rcpv4P8Tu6Y2bRuGqYUGQM0lHjyK_nD8SWKA
The access token supports the following parameters:
| Parameter | Description | Value |
|---|---|---|
td-reg | Allows access to restricted content for this listener. | true = access allowed. |
td-ads | Controls how many ads are inserted for this listener. | nopreroll = no preroll ad insertion, but mid-roll and post-rolls can be inserted. none = no ad insertion at all. |