TTL and expiry

​

TTL and expiry

​

Default TTL by plan

​

Expiry warning webhook

{
  "type":    "vault.expiring",
  "eventId": "evt_clx1abc123",
  "payload": {
    "vaultId":   "vlt_clx1abc123",
    "expiresAt": "2026-05-01T10:00:00.000Z"
  }
}

​

Extend TTL without persisting

import { extendVaultTtl } from '@prudra/vault';

await extendVaultTtl({
  vaultId:  'vlt_clx1abc123',
  ttlHours: 48,  // new TTL from now — must not exceed plan maximum
});

curl -X POST https://api.prudra.dev/vaults/vlt_clx1abc123/extend \
  -H "Authorization: Bearer prv_test_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "ttlHours": 48 }'

​

Persist to survive past TTL

import { persistVault } from '@prudra/vault';
await persistVault({ vaultId: 'vlt_clx1abc123' });

​

What happens on expiry

1. All documents are deleted from the database
2. All files are deleted from GCS (CDN URLs become invalid)
3. All vault events are purged
4. The vault ID returns 404 on any subsequent request
5. A vault.expired webhook fires

​

Error handling

​

Related

• Persist a vault — prevent expiry permanently
• Vault quota — active and persisted vault counts
• Webhooks event reference — vault.expiring and vault.expired