During development, you can use the developer endpoints without an API key. For production use, you’ll need an API key to avoid rate limits.
Using Your API Key
Include your API key in all requests to the APIs by setting thex-api-key header.
All production deployments must use an API key, otherwise you will be rate limited.
GET request
GET request
For GET requests, include the API key in the request headers:
POST request
POST request
For POST requests, include the API key alongside other headers:
WebSocket Authentication
WebSocket connections require both an API key and a WebSocket endpoint. Apply for credentials at https://pond.dflow.net/build/api-key. When using WebSockets, include your API key in thex-api-key header rather than a URL query parameter.
Security Best Practices
- Store your API key securely using environment variables.
- Never commit API keys to version control.
- Rotate your API key if it’s ever exposed.
Getting Help
If you need an API key or have questions about rate limits, reach out to us.API Routes
Cookbook Repository
This recipe, along with many more, is available in the DFlow Cookbook Repo. You can clone it and start coding immediately.Need Help?
Email Support
Reach out to our team at [email protected] for technical support,
partnership inquiries, or general questions.
Join Our Discord
Connect with other developers, get help, and stay updated on the latest
DFlow developments.
Dev Notifications
Join the DFlow Dev Notifications Telegram group to stay in the loop on
new features and other announcements.