DocFlow API Reference
183 endpoints across 18 categories. Every operation available via a single POST request.
Authentication
All API requests require an API key. Include it in the X-API-Key header with every request.
HTTP Header
X-API-Key: df_your_api_key_hereYou can also pass the key as a Bearer token or ?apiKey= query parameter, but the header method is recommended.
Token System
Each operation costs tokens. Tokens are deducted on successful completion only. Response headers include:
X-Tokens-Used— tokens consumed by this requestX-Tokens-Remaining— your remaining balance
Base URL
https://docbutterfly.com
All endpoint paths below are relative to this base URL.
Error Codes
| Status | Meaning | Resolution |
|---|---|---|
400 | Bad Request | Check your request body and parameters |
401 | Unauthorized | Invalid or missing API key |
402 | Payment Required | Insufficient tokens — top up your balance |
403 | Forbidden | Account deactivated |
500 | Server Error | Internal error — contact support |
503 | Service Unavailable | Required service not configured (e.g. Graph API, DocuSign) |
Rate Limits
Currently there are no hard rate limits. The Azure Functions Consumption plan handles auto-scaling. Heavy operations (browser-based) may take 3-10 seconds on cold start.