Skip to main content
The Inheribase API lets you programmatically manage vaults, assets, guardians, and heirs. The base URL for all requests is https://api.inheribase.com. All endpoints follow REST conventions and return JSON responses.

Authentication

Every request requires your Inheribase API key in the x-api-key header.

Key types

Generate keys from Dashboard → Settings → API Keys.

Response format

All successful responses use this envelope structure:
Error responses include an error object with a machine-readable code:

Error codes

Rate limits

Rate-limited responses include a Retry-After header with the number of seconds to wait before retrying.

Types

The following TypeScript interfaces describe the shape of objects returned by the API.

Endpoints

Vaults

List vaults

Returns all vaults owned by the authenticated user.
Response 200 OK:

Get vault details

Returns the full details for a single vault, including timestamps and current state.
Response 200 OK:

Update release configuration

Configure the trigger type and check-in frequency for a vault’s release mechanism. Request body:
Response 200 OK:

People

Add guardian

Sends an invitation email to the specified guardian. Guardians participate in Shamir’s Secret Sharing (SSS) to protect your vault key. Request body:
Response 201 Created:
Errors:
  • 409 — A guardian with this email address already exists on this vault.
  • 400 — Guardian limit reached for the current SSS preset.

Remove guardian

Removes a guardian from the vault and regenerates SSS shares for the remaining guardians. Response 200 OK:

Add heir

Adds an heir to the vault. Heirs receive access to your vault contents when a release is triggered. Request body:
Response 201 Created:
Errors:
  • 409 — An heir with this email address already exists on this vault.
  • 400 — Maximum 5 heirs per vault.

Remove heir

Removes an heir from the vault. Response 200 OK:

Assets

Upload asset

Upload an encrypted asset to the vault. Files must be encrypted client-side before upload. Consult the MCP Server guide if you want encryption handled automatically by an AI assistant. Request body (multipart/form-data): Response 201 Created:
Errors:
  • 402 — Insufficient credits for the file size.
  • 400 — File exceeds the 5 GB limit.

List assets

Returns a paginated list of assets stored in the vault. Query parameters: Response 200 OK:

Release

Check in (reset DMS timer)

Records an Audit Pulse that confirms you are active and resets the Dead Man’s Switch countdown. Each check-in costs 2 Vault Credits ($0.02). Request body (optional):
Response 200 OK:
Errors:
  • 402 — Check-in costs $0.02 (2 credits) — top up your balance to proceed.

Cancel release

Cancel an active release during the 30-day contestation period. You cannot cancel a release after the contestation period has elapsed. Response 200 OK:
Errors:
  • 409 — Vault is not in releasing state, or the contestation period has elapsed.

Deprecated endpoints (v1.0)

The following endpoints were removed in v2.0 as part of the API simplification.
Webhook support for real-time event notifications is planned for a future release. In the meantime, poll GET /api/vault/:id to monitor vault state changes.