Access control
Vaults are private by default — only requests authenticated with your API key can read them. To share a vault with a client (e.g., give the caller access to their results), issue a short-lived vault access token.Issue a vault access token
- SDK
- cURL
Using the access token
The client uses the access token as a Bearer token to read vault contents:Access token permissions
Vault access tokens are read-only — they allow:- Reading vault metadata (
GET /vaults/:id) - Listing and reading documents
- Downloading files
- Subscribing to the SSE event stream
Typical pattern: return token in response
Issue the access token in your payment handler and return it alongside the vault ID:Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
vaultId | string | Yes | The vault to grant access to |
ttlSeconds | number | No | Token lifetime in seconds (default: 3600; max: 86400) |
Related
- Events — subscribe SSE — using access tokens to subscribe to events
- Seal a vault — finalising work before sharing

