JavaScript
TypeScript
Python
PHP
JavaSave the record token
Add the returned UUID to the matching application row. Business data and joins stay in your database.
customer_id: 1024
user_token: "a21fa1d3-8b4c-…"FOR DEVELOPERS
Create a record.
Keep the reference.
Start with sample data through REST or an official SDK. Then build authorized retrieval into the places your application needs the original profile.
BUILT FOR YOUR ENGINEERING TEAM
Your first
vaulted profile.
This example creates a customer record. The response contains its reference; save that alongside your existing application data.
POST /v2/UserCreate
RESPONSE
{
"status": "ok",
"token": "a21fa1d3-8b4c-4e6f-9a2d-6c8e0f1b3d5a"
}Store the token. Retrieve the profile when authorized.
Example values · Replace the host and access credential
100Mrecords in published
PostgreSQL load tests
PostgreSQL load tests
~14 msmedian record retrieval
in the 10M-record benchmark
See the setup and methodology Vendor benchmarks. Results depend on your workload.in the 10M-record benchmark
COMPLETE THE ROUND TRIP
Store the reference.
Retrieve with permission.
These examples illustrate the integration. They don’t contact a vault or send customer data from this website.
Request the profile
Your backend calls UserGet with the record token and a separate, scoped API credential.
POST /v2/UserGet
X-Bunker-Token: <scoped credential>
Content-Type: application/json
{ "mode": "token",
"identity": "<record UUID>" }Use the allowed response
Apply permissions for the calling service. Disallowed string fields can return as ***; other disallowed types are omitted.
{ "name": "Alex Morgan",
"email": "***" }Ready for implementation details?
Open the UserGet referenceKEEP BUILDING
The next pieces of your integration.
Scope access
Connect role credentials to policies and test the fields each application can retrieve.
Read the guide ↗Attach a document
Store customer-linked files and choose their encrypted storage backend.
Read the guide ↗Use an official SDK
JavaScript / TypeScript, Python, PHP and Java SDKs are documented.
Read the guide ↗Migrate existing records
Backfill profiles, verify the mapping, and update application reads and writes.
Read the guide ↗Start with scoped access. Keep API credentials in your backend environment. Root credentials are privileged; application access should use the permissions intended for that service.
LESS SPRAWL. MORE CONTROL.
Give sensitive data
a proper home.
Walk through your architecture with a Databunker engineer.
Find the right place to start.