Skip to main content
Databunker Pro is a privacy-compliant user data vault and tokenization engine that provides secure storage and management of user data with built-in privacy controls, consent management, and audit capabilities.

​
API Documents for AI Assistants

Feed these directly into your LLM or AI coding assistant for accurate, context-aware help when building integrations:

​
Key Features

  • User Tokenization: Create, update, and manage user profiles with privacy controls
  • Consent Management: Handle legal basis and user agreements for GDPR/DPDP compliance
  • Format Preserving Tokenization: Secure tokenization of sensitive data like credit cards
  • File Storage: Encrypted per-user file storage backed by local disk, Amazon S3, Google Cloud Storage, or Azure Blob Storage
  • Audit Trail: Complete audit logging of all data access and modifications
  • Multi-tenant: Support for multiple tenants with isolated data
  • Role-based Access: Fine-grained access control with policies and roles
  • Bulk Operations: Efficient bulk data operations with unlock mechanisms

​
Authentication

All API calls require authentication via the X-Bunker-Token header. For multi-tenant setups, use the X-Bunker-Tenant header to specify the tenant context. For the full credential hierarchy — root tokens, tenant tokens, role and user xtokens, and the bulk-unlock UUID — see the Authentication reference.

​
Multi-Tenant Usage

Multi-tenancy is supported on PostgreSQL, MySQL (Percona), and Oracle backend databases. On PostgreSQL it is enforced with the database’s native row-level security (RLS). When using Databunker Pro in a multi-tenant environment:
  • Single Tenant: Omit the X-Bunker-Tenant header (default behavior)
  • Multi-Tenant: Include X-Bunker-Tenant: your-tenant-name header
Example:

​
Base URL

The API is available at /v2/ endpoint with all requests using POST method.

​
Error Handling

Every error is returned as {"status":"error","message":"..."} with a conventional HTTP status code (400/403/404/409/500). See the full Errors reference for the status-code table and a catalog of common messages.

​
Pagination

List endpoints accept offset/limit in the request body and return a {status, total, rows} envelope. See the Pagination reference.