API keys
Connect your bot, server or application to Veil. All keys belonging to one card share its allowance.
Use your Veil card
An active device signs requests to create and manage API keys.
Owner card
API access for this card is suspended. Creating another key will not restore it.
Account limits
These limits apply across every key owned by this card. Daily allowances reset at midnight UTC.
Integration keys
To rotate a key, create a replacement, update your integration and revoke the old key. The shared allowance stays the same.
Create an API key
Public reads: look up cards, read their keys, history and the log. Message verification: check a signed message with POST /v1/verify. API keys do not grant permission to change a card or use staff tools. Keep the secret on your server. It is shown once and cannot be retrieved later. Websites can use the public API without a key.
Save this secret now
This is the only time Veil will show it. Put it in your server’s secret configuration.
Request history
Admitted requests count even if the endpoint returns an error. Rejected requests here were blocked by an API quota.
Private activity
Each key change keeps its signed request and a private receipt. These events are not published in the identity log.