Seal a vault

Sealing a vault marks work as complete. After sealing:

No further documents, files, or events can be written
The SSE event stream closes, signalling to subscribers that the job is done
The vault enters a read-only state while its TTL continues to count down

Sealing via vaultMiddleware

When using vaultMiddleware, call vault.seal() before responding:

app.post('/analyse', walletMiddleware(...), payMiddleware(...), vaultMiddleware(), async (req, res) => {
  const vault = req.vault!;

  await vault.addDocument({ result: 'done' }, 'Analysis result');

  // Seal before responding — closes SSE stream, marks vault read-only
  await vault.seal('Analysis complete');

  res.json({ vaultId: vault.id });
});

Sealing via API

SDK
cURL

import { initialise } from '@prudra/core';
import { sealVault } from '@prudra/vault';

initialise({ apiKey: process.env.PRUDRA_API_KEY! });

await sealVault({
  vaultId: 'vlt_clx1abc123',
  summary: 'Processed 47 items successfully',
});

curl -X POST https://api.prudra.dev/vaults/vlt_clx1abc123/seal \
  -H "Authorization: Bearer prv_test_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "summary": "Processed 47 items successfully" }'

Response:

{
  "id":       "vlt_clx1abc123",
  "status":   "sealed",
  "summary":  "Processed 47 items successfully",
  "sealedAt": "2026-04-30T09:05:00.000Z"
}

Parameters

Parameter	Type	Required	Description
`vaultId`	string	Yes	The vault to seal
`summary`	string	No	Human-readable summary stored on the vault record

What sealing triggers

When a vault is sealed, Prudra fires a vault.sealed webhook to all registered webhook URLs:

{
  "type":    "vault.sealed",
  "eventId": "evt_clx1abc123",
  "payload": {
    "vaultId": "vlt_clx1abc123",
    "summary": "Processed 47 items successfully",
    "sealedAt": "2026-04-30T09:05:00.000Z"
  }
}

Use this webhook to notify your users that results are ready, or to trigger downstream processing.

Sealing before the job finishes

If your handler responds before work is complete (e.g., streaming results asynchronously), do not seal immediately. Seal only when all writes are done:

res.json({ vaultId: vault.id });  // respond first

setImmediate(async () => {
  // Continue working after response
  for (const item of items) {
    await vault.emit('progress', { item });
  }
  await vault.seal('All items processed');  // seal when truly done
});

Events — SSE stream that sealing closes
Persist a vault — extend lifetime after sealing
Webhooks event reference — vault.sealed payload schema

Get Started

Payments

Wallets

Storage

Webhooks

Discovery

Platform

Seal a vault

Seal a vault

Sealing via vaultMiddleware

Sealing via API

Parameters

What sealing triggers

Sealing before the job finishes

​Seal a vault

​Sealing via vaultMiddleware

​Sealing via API

​Parameters

​What sealing triggers

​Sealing before the job finishes

​Related

Seal a vault

Sealing via vaultMiddleware

Sealing via API

Parameters

What sealing triggers

Sealing before the job finishes

Related