# Create a playback token key

This operation creates a playback token key that includes a key id and key value. You use one or both of these parameters to create a playback token for advanced token authentication. 

Before using the ADVANCED_TOKEN option as your token authentication for a video, you must do one of the following: 

 - Generate a playback token key that has a key id using this endpoint in the Wowza Video API, then customize and generate a token via the Wowza Video 2.0 API to add to your site. You'll need the key id to create and sign the token.  
 - Generate a playback token key that has a key id and key value using this endpoint in the Wowza Video 2.0 API, then customize and generate a standard common access token (CAT) through the means you usually use to create tokens to add to your site. You'll need the key id and key to create and sign the token.  
   The key value is only returned in this endpoint so keep it in a place that you can access it later when you create your playback token.

Endpoint: POST /playback_tokens/keys
Version: v2.0

## Request fields (application/json):

  - `playback_token_key` (object)

  - `playback_token_key.name` (string, required)
    The name of the playback token key for the organization.
    Example: "Key name"

## Response 200 fields (application/json):

  - `playback_token_key` (object)

  - `playback_token_key.id` (string)
    Unique identifier for the playback token key. The id will contain the organization id in the key id.
    Example: "51cd5c07-1583-4f5e-bd81-f1aa11510ea9"

  - `playback_token_key.organization_id` (string)
    The organization id for Wowza Video.
    Example: 123456

  - `playback_token_key.name` (string)
    The name of the key for the organization.
    Example: "key name"

  - `playback_token_key.created_at` (string)
    The key creation timestamp.
    Example: "2020-01-01T12:33:22Z"

  - `playback_token_key.value` (string)
    The key value for the key.

If you generate a playback token for advanced token authentication by creating a  standard common access token (CAT) through the means you usually use to create tokens, you'll need to add this key value during token creation to sign the token. The key  value is only returned in this endpoint to keep it in a place that you can access it later when you create your playback token.

## Response 401 fields (application/json):

  - `meta` (object, required)

  - `meta.status` (integer)

  - `meta.code` (string)

  - `meta.title` (string)

  - `meta.message` (string)

  - `meta.description` (string)

  - `meta.links` (array)

## Response 403 fields (application/json):

  - `meta` (object, required)

  - `meta.status` (integer)

  - `meta.code` (string)

  - `meta.title` (string)

  - `meta.message` (string)

  - `meta.description` (string)

  - `meta.links` (array)

## Response 404 fields (application/json):

  - `meta` (object, required)

  - `meta.status` (integer)

  - `meta.code` (string)

  - `meta.title` (string)

  - `meta.message` (string)

  - `meta.description` (string)

  - `meta.links` (array)

## Response 410 fields (application/json):

  - `meta` (object, required)

  - `meta.status` (integer)

  - `meta.code` (string)

  - `meta.title` (string)

  - `meta.message` (string)

  - `meta.description` (string)

  - `meta.links` (array)

## Response 422 fields (application/json):

  - `meta` (object, required)

  - `meta.status` (integer)

  - `meta.code` (string)

  - `meta.title` (string)

  - `meta.message` (string)

  - `meta.description` (string)

  - `meta.links` (array)