> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tokenize data with the CryptoHub REST API

> Use-case overview for tokenizing and detokenizing data through the CryptoHub v2 REST API against an administrator-defined token profile.

In CryptoHub 7.3.0.x, tokenization is split between two roles. An administrator defines a **token profile** and its **Control Rules** in the CryptoHub client; an application then submits data to that profile through the API. You do not build the transformation per request: you select a profile by its UUID and call its endpoints.

## Prerequisites

Before an application can tokenize or detokenize, an administrator must have:

* Created a token profile with a backing key. See [Create a tokenization profile](/CryptoHub/7.3.0.x/Administrator_guide/Data_protection/Tokenization/Managing_tokenization/Create_a_tokenization_profile).
* Added at least one Control Rule on the profile's Access tab that grants your role the operation you intend to run. See [Control rules and access](/CryptoHub/7.3.0.x/Administrator_guide/Data_protection/Tokenization/Tokenization_profiles/Control_rules_and_access).

## Steps

1. [Enable API access](/REST_API/Docs/Use_cases/Tokenization/Enable_API_access) and authenticate to the v2 REST API or the Host API.
2. [Tokenize and detokenize data](/REST_API/Docs/Use_cases/Tokenization/Tokenize_and_detokenize_data) against the profile by its UUID.

For the request and response schema of every endpoint, see the [token-profiles API reference](/REST_API/Docs/Key_management/Token_profiles).