# Request cryptogram

Request a cryptogram (TAAV) for a given network token. The cryptogram is a dynamic value used to 
authenticate and authorize tokenized transactions, ensuring secure communication with the payment network.

Guardian supports two types of scenarios for cryptograms:

{% table %}

- Type {% width="20%" %}
- Description

---

- 
- This type is used in standard e-commerce transactions when a network token is in use.

---

- 
- This type is based on a delegated authentication setup with the card schemes and requires prior activation.

{% /table %}


Endpoint: POST /api/network/tokens/{id}/cryptograms
Version: EAP
Security: APIKey, AdminToken

## Path parameters:

  - `id` (string, required)
    The ID of the token for which to request a cryptogram.

## Header parameters:

  - `x-idempotency-key` (string)
    Optional idempotency key to prevent duplicate processing
    Example: "order_12345_retry_001"

## Response 200 fields (application/json):

  - `cryptogram` (string, required)
    The token authentication verification value (TAVV) for the network token.
    Example: "Af9KZ3vVQkFxM3BZkJYFZkYBAgAEAAAB"

  - `eci` (string, required)
    The Electronic Commerce Indicator (ECI) from the issuer.
    Example: "05"

  - `expiry_month` (integer, required)
    Example: 10

  - `expiry_year` (integer, required)
    Example: 2030

  - `number` (string, required)
    Example: "4122234533471157"

  - `metadata` (object)
    Metadata consisting of entries, each of which each includes a key and an associated value:

  * Maximum 20 key-value pairs.
  * Maximum 20 characters per key.
  * Maximum 80 characters per value.
    Example: {"my_key_one":"my_value_one","my_key_two":"my_value_two"}

## Response 400 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 401 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 403 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 404 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error