https://api.inheribase.com. All endpoints follow REST conventions and return JSON responses.
Authentication
Every request requires your Inheribase API key in thex-api-key header.
Key types
Generate keys from Dashboard → Settings → API Keys.
Response format
All successful responses use this envelope structure: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
200 OK:
Get vault details
200 OK:
Update release configuration
200 OK:
People
Add guardian
201 Created:
409— A guardian with this email address already exists on this vault.400— Guardian limit reached for the current SSS preset.
Remove guardian
200 OK:
Add heir
201 Created:
409— An heir with this email address already exists on this vault.400— Maximum 5 heirs per vault.
Remove heir
200 OK:
Assets
Upload asset
multipart/form-data):
Response
201 Created:
402— Insufficient credits for the file size.400— File exceeds the 5 GB limit.
List assets
Response
200 OK:
Release
Check in (reset DMS timer)
200 OK:
402— Check-in costs $0.02 (2 credits) — top up your balance to proceed.
Cancel release
200 OK:
409— Vault is not inreleasingstate, 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.