Updated on December 21, 2023


Unmasking in tokenization refers to the process of reversing the tokenization procedure to retrieve the original sensitive data from its tokenized form. It is the opposite of tokenization, where sensitive information is replaced with tokens to enhance security and privacy.

Endpoint and Authentication:

To use Protecto.ai’s token-based masking, you need to send a PUT request to the following endpoint:

Endpoint: https://trail.protecto.ai/api/vault/unmask

For authentication, include the following token in the request headers:

Headers: {“Authorization”: “Bearer <AUTH_TOKEN>”}

Request Payload:

Here’s an example of a request payload to unmask  data:

Request Payload:
{"unmask":[{"token_value":"8oGEcGVEkj 700ZSgo1pA"}]}
Parameters :
  • token_value (string): The token for which the original value needs to be retrieved.
Response :
    "data": [
            "token_value": "8oGEcGVEkj 700ZSgo1pA",
            "value": "George Williams"
    "success": true,
    "error": {
        "message": ""
 Response Parameters:
  • token_value (string): The original token that was provided in the request.
  • value (string): The original sensitive data value retrieved from the token.

Advantage :

Authorized Data Access: Unmasking allows authorized personnel to access the original, unmasked data when needed, while still keeping the data protected during other stages of processing or storage.

Note : Unmasking should be performed under strict controls, only by authorized individuals, and in compliance with data protection policies and regulations. Organizations should carefully weigh the benefits and risks of unmasking, based on their specific use cases and security requirements.

What are your feelings?
Scroll to Top