Integrate Veil
Find the right key through an account your users already know. Let them check who signed a message, even if that account is stolen.
A card, read live#
GET
https://veil.rip/u/1.jsonThis request runs as the page opens. Its answer fills the values below.
| Field | In this answer | Meaning |
|---|---|---|
n | integer | Permanent card number. |
name | string | Current display name; a hidden name becomes Card followed by its number. |
url | string | Permanent URL using the card number. |
keys | array<CardKey> | All device and recovery keys, including revoked keys. |
fingerprint | Fingerprint | Twelve words in each language and twelve five-digit groups. |
witnesses | object | null | signed, of and needed counts for the current version. These are server checks. |
The whole answer
Public lookups, cards and message verification need no API key. You can call them from a browser, a bot or a server.
cURL
curl -fsS 'https://veil.rip/u/1.json'Common tasks#
- GETLook up a cardFind the card that holds one exact account, key or fingerprint.
/v1/lookup - GETRead a person’s cardRead the full public card, signed record, proof and recent history.
/u/{card}.json - GETFind the owner of a keyLook up a public key, the card holding it and its validity period.
/v1/keys/{key} - POSTVerify a messageCheck a signature block or an explicit key, message and signature. This POST only reads.
/v1/verify - POSTVerify a file or a releaseCheck the signature of a file from its hash, or of a signed checksum list, against a card’s keys. This POST only reads.
/v1/verify - GETCheck when a key could signAsk whether a key was active at a particular time.
/v1/keys/{key}/active-at - GETRead card historyRead older version events and the account transfers around them.
/v1/identities/{n}/history - GETEmbed a verifying widgetShow a read-only card that verifies itself in the visitor’s browser.
/{kind}/{card}/embed
Use the result#
- Choose a linked badge, an image or a widget that checks the card.
- Check the exact text, its signing key and that key’s state.
- Look up cards and check signed messages in any Discord server or DM.
- Use fetch directly for public reads and message verification.
- Check a card’s signed versions, its place in the log’s index and the witnesses behind the log.
- Install veil from the signed apt repository, winget or Homebrew, and check the repository key against the Veil organisation’s card.
Browse the reference#
- Public reads, integration resources and requests available to card owners.
- Use an authorised device key for changes to cards and organisations.
- Keep requests bounded and follow the response when a call needs to wait.
- Give a server integration a shared allowance without granting authority over a Veil card.