Which API endpoint should I use?
Last updated: June 12, 2026
The BFL API is available on a global endpoint and two regional endpoints. All of them accept the same requests and return the same results; they differ only in where traffic is routed.
Endpoint | Routing | Use it for |
api.bfl.ai | Global, with automatic failover across clusters | Default choice for most integrations. |
api.eu.bfl.ai | EU regions only, GDPR compliant | European traffic or EU data-residency needs. |
api.us.bfl.ai | US regions only | US traffic that benefits from staying in-region. |
Always use the returned polling_url
When you submit a request, the response includes a polling_url. Poll that exact URL to retrieve your result. It already points at the region that handled your request, so do not rebuild it or swap the host yourself.
Picking a region
Choosing the region closest to your traffic can reduce latency. If you have no specific residency requirement, the global api.bfl.ai endpoint is the simplest option and load-balances for you.
Downloading results
Generated images are served from delivery URLs that expire after 10 minutes. Download your result promptly, and if you use firewall rules, allow the wildcard delivery.*.bfl.ai (or all of *.bfl.ai) rather than individual regional hostnames, which can change.