Account

Register (or rotate) the public key Tuteliq uses to encrypt your incident records

Registers an RSA public key. After registration, all NEW incident records (rationale, visual_description, etc.) are encrypted with a per-record AES key, which is itself wrapped with this RSA key (hybrid scheme RSA-OAEP + AES-256-GCM). Tuteliq cannot decrypt — only your dashboard (with the matching private key) can.

Rotating: POST a new key here. New incidents use the new key; old incidents remain readable with the old private key until they expire (90 days).

Private key is YOUR responsibility — Tuteliq cannot recover lost-key incidents.

post/api/v1/account/encryption-key

Request

  • Base URL: https://api.tuteliq.ai
  • URL: https://api.tuteliq.ai/api/v1/account/encryption-key
  • Auth: one of:
    • HTTP bearer
    • API key in header x-api-key

Request body

algorithm'RSA-OAEP-2048' | 'RSA-OAEP-4096' required

RSA-OAEP key size. 2048-bit is faster, 4096-bit is more conservative.

public_key_pemstring required

PEM-encoded SPKI public key (begins with "-----BEGIN PUBLIC KEY-----").

Response

Default Response

algorithmstring
public_key_pemstring
key_fingerprintstring
registered_atstring
rotated_fromstring

Changes

No recorded changes to this operation across all 1 revision of this API.