Introduction

The VGS Vault HTTP API is used for storing, retrieving, and managing sensitive data within a VGS Vault (aka Tokenization). VGS's Tokenization platform assigns aliases to real values and stores them as key/value pairs in each vault. There are several configurations that determine the storing behavior of VGS vaults and subsequently the behavior of this api. Specifically:

• Fingerprinting

  Fingerprinting, when configured to on, will ensure that a value will always return the same alias for any alias type. For instance, if one were to tokenize the string ABC123 using an alias format of UUID the api would return an alias like this tok_live_553468dafgda6asdfa5fa. Every subsequent "create alias" on the same value will return the same alias tok_live_553468dafgda6asdfa5fa. When configured to off, each create alias will create a new and separate UUID for this value. Fingerprinting can be configured in the VGS dashboard in a vault's advance settings.

• Reveal

  For read operations to work on any vault - VGS needs to configure each vault to allow for read access. Even if you were to apply the vault:read scope.