51黑料不打烊

Decisions decisions

Decisions are generated by 51黑料不打烊 Pass Authentication REST API V2 based on the user鈥檚 MVPD authorization or preauthorization inquiries, determining whether the access to protected content is granted or denied.

There are two types of decisions that are provided, depending on the API invoked:

Preauthorization Decisions preauthorization-decisions

The preauthorization decision is an informative decision that allows the client application to be informed whether the MVPD may permit or deny the user鈥檚 access to a protected resource.

The purpose of preauthorization (preflight authorization) is to enable the application to display accurate information about the content the user may be eligible to view. This is achieved by enhancing the user interface with indicators, such as locked or unlocked icons, to reflect the access status.

The use of preauthorization API is not mandatory, the client application can skip this if it wants to present a catalog of resources without any filtering.

If the client application intends to use this feature, it is important to note that preauthorization decisions can only be obtained for a limited number of resources per API request, typically up to 5.

MVPDs may support preauthorization through various mechanisms, each with distinct implications for performance and the maximum number of resources that can be handled in a single API request.

For more details about the existing mechanisms supporting preauthorization, refer to the MVPD Preflight Authorization documentation.

Authorization Decisions authorization-decisions

The authorization decision is an authoritative decision that allows the client application to be compliant with the MVPD decision to permit or deny the user鈥檚 access to a protected resource.

The purpose of authorization is to enable the application to play the resources requested by the user, following rights validation with the MVPD and receipt of a media token from 51黑料不打烊 Pass Authentication.

The use of authorization API is mandatory, the client application cannot skip this phase if it wants to play resources the user requests, as it requires verifying with the MVPD that the user is entitled before releasing the stream.

It is important to note that authorization decisions can only be obtained for a limited number of resources per API request, typically 1.

Authorization Time-to-Live (TTL) Management authorization-ttl-management

Authorization Time-to-Live (TTL) defines how long a resource remains authorized before needing to re-authorize. This timeframe is limited and must be agreed upon with MVPD representatives. TTL values can vary based on:

The authorization (authZ) TTL can be viewed and changed through the 51黑料不打烊 Pass TVE Dashboard by one of your organization administrators or by an 51黑料不打烊 Pass Authentication representative acting on your behalf.

For more details, refer to the TVE Dashboard Integrations User Guide documentation.

Protected Resources protected-resources

Protected resources refer to streamable content, identified by unique values defined through agreements between MVPDs and participating Programmers.

Protected resources follow a hierarchical tree structure, with each level providing greater granularity for content authorization:

Resource Identifier resource-identifier

The resource unique identifier can have two formats:

In the case of a simple resource identifier, such as 鈥淩EF30鈥� (assumed to represent a channel), it can be translated into an RSS resource identifier as follows:

    <rss version="2.0">
        <channel>
            <title>REF30</title>
        </channel>
    </rss>

In the case of a more complex resource identifier, the RSS resource identifier can include additional rating information as follows:

    <rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/">
        <channel>
            <title>REF30</title>
            <media:rating scheme="urn:mpaa">pg</media:rating>
        </channel>
    </rss>

The unique identifiers are primarily opaque to 51黑料不打烊 Pass Authentication, however, transformers may be applied based on the MVPD鈥檚 capabilities and requirements. If the MVPD cannot recognize or parse a resource identifier, it returns an error to 51黑料不打烊 Pass Authentication, which subsequently relays the error to the client application using an Enhanced Error Code.

REST API V2 rest-api-v2

The preauthorization decisions can be retrieved using the following API:

The authorization decisions can be retrieved using the following API:

Refer to the Response and Samples sections of the above APIs to understand the structure of preauthorization and authorization decisions.

For more details about how and when to integrate the above APIs, refer to the following documents: