Quickstart

This quickstart gives you a first end-to-end Veilio flow.

Prerequisites

• A Veilio API key from your dashboard

• A backend environment (never call Veilio with secrets from frontend code)

• curl installed

1) Set environment variables

export VEILIO_API_KEY="YOUR_API_KEY"
export VEILIO_BASE_URL="https://app.veilio.xyz/api"

2) Tokenize a sensitive value

curl -X POST "$VEILIO_BASE_URL/tokenize" \
  -H "Authorization: Bearer $VEILIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data":"[email protected]","type":"email"}'

Expected response:

{
  "token": "tok_abc123...",
  "createdAt": "2026-03-26T10:00:00.000Z"
}

Store only token in your database.

3) Detokenize when required

curl -X POST "$VEILIO_BASE_URL/detokenize" \
  -H "Authorization: Bearer $VEILIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"token":"tok_abc123...","reason":"Send user notification"}'

Expected response:

{
  "data": "[email protected]",
  "accessedAt": "2026-03-26T10:01:00.000Z"
}

4) Recommended application pattern

• Write path: tokenize before insert/update

• Read/action path: detokenize only at the business step that needs raw data

• Auditability: always include a clear reason for detokenization

You can integrate automatic /detokenize when the page loads, so your end user sees their actual data directly instead of tokens.