Screener 2FA Registration

watch.content.screener_2fa.register

If the screener has two-factor authentication (phone verification) security enabled, this endpoint will be used to register the user's phone number to be linked with it.

Endpoint

POST v2/watch/content/screeners/{screener_key}/2fa

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

    {
        "phone": <int>,
        "country_code": <int>
    }

Parameter	Type	Requirement	Description
phone	Integer	Required	Phone number of the user to whom the 2FA registration is being linked.
country_code	Integer	Required	Country code of the user's phone number.

Response Body

    {
        "status_code": "W0000",
        "status_message": "Success"
    }

Field	Type	Description
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
W2001	HTTP 401	API key is invalid or expired, or is not fully configured
W2003	HTTP 401	Invalid or expired auth token
W2007	HTTP 401	Viewer sign-in is required for this screener
W2009	HTTP 401	ClientID header was either not passed or is malformed
W2100	HTTP 403	Not authorized for this screener. Raised when the origin domain is not whitelisted, the screener has expired or reached its view limit, two-factor authentication is not enabled on the screener, or the screener does not belong to the enterprise the API key or viewer resolves to
W2108	HTTP 403	Watch product is inactive
W2102	HTTP 451	Request blocked by geofencing for the resolved region
W4200	HTTP 400	The screener key does not exist, or the screener does not belong to the signed-in viewer
W4900	HTTP 400	Malformed request body. phone or country_code was missing or was not an integer
W5001	HTTP 429	Rate limited
W5000	HTTP 500	Unknown server error occurred