Tokenize data with the CryptoHub REST API

This use case shows how an application tokenizes and detokenizes data through the CryptoHub REST API. 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.
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.

Steps

Enable API access and authenticate to the v2 REST API or the Host API.
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.

​Prerequisites

​Steps

Prerequisites

Steps