MinakiLabs API
Cryptographic proof, document security, and zero-knowledge storage — all on MinakiChain.
Overview
The MinakiLabs API gives developers programmatic access to all six MinakiLabs products. Every request is authenticated with an API key and proxied through Kong Gateway. All responses are JSON.
🔒 ReserveProof
Crypto proof-of-reserves
📄 DocProof
Document notarization on-chain
🔍 AuditTrail
Immutable compliance logs
✍️ SignatureProof
Ed25519 document signing
🗄️ DocumentVault
AES-256 encrypted file storage
🔑 CredVault
Zero-knowledge password vault
Authentication
All API requests require an API key passed in the apikey header. Get your key from the MinakiLabs dashboard.
apikey: your-api-key-here
# Example request
curl https://api.minaki.io/v1/docproof/health \
-H "apikey: your-api-key-here"
Base URL
https://api.minaki.io/v1
Errors
Rate Limits
Rate limit headers are returned on every response:
RateLimit-Limit: 60
RateLimit-Remaining: 59
RateLimit-Reset: 60
X-RateLimit-Limit-Minute: 60
X-RateLimit-Limit-Hour: 1000
ReserveProof
Submit and verify cryptographic proof-of-reserves. Anchored to MinakiChain.
DocProof
Notarize documents by anchoring their SHA-256 hash to MinakiChain.
curl -X POST https://api.minaki.io/v1/docproof/api/documents \
-H "apikey: your-key" \
-H "Content-Type: application/json" \
-d '{"filename":"contract.pdf","sha256":"abc123...","owner_email":"you@example.com"}'
AuditTrail
Write immutable compliance events anchored to MinakiChain. Tamper-evident.
SignatureProof
Create multi-party Ed25519 signature requests and verify cryptographic signatures.
DocumentVault
Store AES-256-GCM encrypted files. Zero-knowledge — files are encrypted client-side before upload.
CredVault
Zero-knowledge encrypted credential storage. Master password never leaves the client.