Developer API
Integrate anon.li directly into your applications using our secure REST APIs.
Anon.li provides developer-friendly REST APIs for both email aliasing and encrypted file sharing. Build privacy-first applications with secure email forwarding and zero-knowledge file encryption.
Getting Started
1. Create an API Key
Generate an API key in your Dashboard. Your key will start with ak_ and should be kept secret. API keys are created and deleted from your signed-in dashboard session; an existing API key cannot create or delete other API keys.
2. Authenticate Requests
Include your API key in the Authorization header:
Authorization: Bearer ak_your_api_key_here
3. Choose Your API
Alias API
Create and manage email aliases programmatically. Forward emails to any inbox while protecting your real address.
Drop API
Upload and share end-to-end encrypted files. Zero-knowledge storage with automatic expiration and download limits.
Form API
Manage end-to-end encrypted forms for confidential intake. Schema-first JSON definitions; submissions decrypt only in your vault.
Base URL
All API endpoints are relative to:
https://anon.li/api/v1
Security Features
- API Key Authentication - Secure Bearer token authentication
- Rate Limiting - Protection against abuse with per-endpoint limits
- Monthly API Quotas - API-key requests count against your Alias or Drop monthly API quota; dashboard actions use separate abuse-prevention limits
- End-to-End Encryption - Drop files are encrypted client-side before upload
- Zero-Knowledge File Sharing - Drop keys stay client-side and do not reach our servers
- Vault-Wrapped Recovery - CLI clients can store only vault-wrapped Drop owner keys and encrypted Alias metadata
- Transient Email Forwarding - Alias forwards mail to your inbox instead of providing hosted mailbox storage
Rate Limits
Rate limits vary by endpoint. When you exceed a limit, you'll receive a 429 Too Many Requests response with headers indicating when you can retry:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1699999999999
Retry-After: 3600
Error Format
All errors follow a consistent format:
{
"error": {
"message": "Error message describing what went wrong",
"code": "VALIDATION_ERROR"
},
"meta": {
"request_id": "req_1234567890abcdef"
}
}
Need Help?
- Check the Alias API documentation for email aliasing
- Check the Drop API documentation for encrypted file sharing
- Connect AI agents (Claude, Cursor, etc.) via the MCP Server — OAuth, no API key paste required
- Contact support at hi@anon.li