Getting Your API Key
Sign in to your Dashboard
Go to verilock.io/dashboard and sign in with your account.
Key Properties
| Property | Type | Description |
|---|---|---|
name | string | Human-readable label for identification |
key | string | The API key value — use in the Authorization: Bearer header |
prefix | string | qi_live_ for production, qi_test_ for sandbox |
created_at | datetime | When the key was generated |
last_used_at | datetime | Last time the key was used for an API call |
Security Best Practices
Use environment variables
Store keys in
VERILOCK_API_KEY env vars. Never hardcode them in source code.Separate environments
Use distinct keys for development, staging, and production. Revoke keys when environments are decommissioned.
Rotate regularly
Rotate production keys quarterly. Create the new key, update your services, then revoke the old key.
Server-side only
Never include API keys in frontend code, mobile apps, or client-side JavaScript. All calls must come from your backend.

