Screener Reactivation Request

watch.content.screener.reactivate

If a screener has expired and can't be watched anymore, this endpoint can be used to request for a reactivation.

Endpoint

POST v2/watch/content/screeners/{screener_key}/reactivate

Headers

If the product does not allow for link type screeners and force-login has been enabled for the screener, a JWT token is mandatory to be passed in the Authorization header.

Note: The force_login flag on the screener currently only applies to Publicity screeners.

Header	Value
Authorization	JWT token

If the product allows link type screeners and the force-login has not been enabled for the screener, the API key can be passed in the Authorization header for authentication.

Header	Value
Authorization	Bearer api_key

Request Body

    {
        "email": "abc@example.com",
        "message": <str>
    }

| Parameter | Type | Requirement | Description | |-----------------|----------------------------|--------|-------------------------------------| | email | String | Required | Email ID of the user for whom the screener reactivation is requested. | | message | String | Required | Message to be displayed to the user regarding the reactivation. |

Response Body

    {
        "message": "Screener activation request sent.",
        "status_code": "W0000",
        "status_message": "Success"
    }

Field	Type	Description
message	String	Confirmation that the reactivation request was sent.
status_code	String	The Indee status code for the response.
status_message	String	Human readable message describing the response.

Status Codes

Indee status code	HTTP Response Code	Description
W0000	HTTP 200	Success
W2000	HTTP 401	Authorization header was either not passed or there was some issue parsing it
W2003	HTTP 401	Invalid auth token
W2101	HTTP 403	API key not authorized to perform this action
W5001	HTTP 429	Rate limited
W5000	HTTP 500	Unknown server error occurred