# Tokenization Token

Tokenization token

```http
200
```
Activate tokenization request successfully delivered to the card network.

# Error Codes

| Code | Description |
| --- | --- |
| `400` | A parameter in the query given in the request does not match the valid queries for the endpoint. |
| `401` | User has not been authenticated |
|       | Invalid or missing API key |
|       | API key is not active |
|       | The API key used is no longer active |
|       | Could not find API key |
|       | The API key provided is not associated with any user |
|       | Please provide API key in Authorization header |
|       | The Authorization header is not in the request |
|       | Please provide API key in the form Authorization: [api-key] |
|       | The Authorization header is not formatted properly |
|       | Insufficient privileges. Issuing API key required |
|       | Write access requires an Issuing API key. Reach out at [lithic.com/contact](/content/contact/index.html) |
|       | Insufficient privileges to create virtual cards. |
| `404` | The specified resource was not found. |
| `409` | The request could not be completed due to a conflict with the current state of the target resource. |
| `429` | Client has exceeded the number of allowed requests in a given time period. |
|       | Rate limited, too many requests per second |
|       | User has exceeded their per second rate limit |
|       | Rate limited, reached daily limit |
|       | User has exceeded their daily rate limit |
|       | Rate limited, too many keys tried |
|       | One IP has queried too many different API keys |

## Example Request

```bash
curl --request POST \
     --url https://sandbox.lithic.com/v1/tokenizations/tokenization_token/activate \
     --header 'accept: application/json'
```

## Responses

- `400`
- `401`
- `404`
- `409`
- `429`

Updated 3 months ago