Signavique
Documentation

API & automation

API keys and authentication

Keys are bound to the person who created them and inherit that person's permissions.

Current service scope: HTML creation and guided installation are available. Transport stamping and on-premises agents are not available; directory connectivity does not deploy outgoing signatures. Review service limitations.

4 min read

Rules

  1. 1Keys are displayed once at creation and stored hashed — we cannot recover one.
  2. 2Send keys in the x-api-key header, never in a query string.
  3. 3Revoke immediately if a key appears in a repository or log.
  4. 4Rotate by creating the new key, switching traffic, then revoking the old one.

Errors

  1. 1401 — missing or invalid key.
  2. 2404 — the resource does not exist or is not yours.
  3. 3422 — the request body failed validation; the response names the field.
Next guideWebhooks