bfl-api

Integrate BFL FLUX API for image generation and editing with webhooks.

46.2k|5.7k|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/calesthio/OpenMontage --skill bfl-api-calesthio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bfl-api
Source: https://github.com/calesthio/OpenMontage/tree/main/.agents/skills/bfl-api
Command: npx skills add https://github.com/calesthio/OpenMontage --skill bfl-api-calesthio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a clear, production-focused integration guide and client patterns for using the BFL FLUX API so engineers can reliably generate and edit images without guessing API behavior, handling transient errors, or mismanaging ephemeral result URLs.

Core Features & Use Cases

  • Endpoint & Region Selection: Guidance on global, EU, and US endpoints and when to choose each for residency/compliance.
  • Async Patterns & Delivery: Polling and webhook architectures with signature verification and hybrid fallback strategies.
  • Resilience & Limits: Rate-limit handling, exponential backoff retries, circuit breaker patterns, and strategies for batch/parallel generation.
  • Use Case: Build a server-side image generation pipeline that submits jobs, automatically retries transient failures, processes webhook notifications, and immediately persists ephemeral result URLs.

Quick Start

Submit a generation request to the appropriate flux-2 model with your BFL_API_KEY, wait for a Ready response via webhook or polling, and download the result immediately because URLs expire in 10 minutes.

Frequently Asked Questions about bfl-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle BFL FLUX API rate-limiting and transient errors in a production pipeline?

Handle BFL FLUX API rate-limiting by implementing exponential backoff retries and circuit breaker patterns to automatically recover from transient failures during batch image generation. This ensures your server-side pipeline processes jobs reliably without exceeding request thresholds.

Why do my BFL FLUX image generation result URLs expire and how do I download them?

BFL FLUX image generation result URLs expire in 10 minutes because they are ephemeral. You must immediately download and persist the generated images upon receiving a Ready response via webhook or polling to prevent data loss in your server-side workflow.

What is the difference between polling and webhooks for asynchronous FLUX image generation?

Polling repeatedly checks job status until completion, while webhooks push a Ready response to your server. Webhooks include signature verification for security, and you can use a hybrid fallback strategy combining both for robust async image generation delivery.

Can I use BFL FLUX API endpoints for specific data residency and compliance regions?

Yes, you can use BFL FLUX API endpoints for specific data residency and compliance regions by selecting global, EU, or US endpoints. Choosing the correct regional endpoint ensures your image generation and editing workflows meet local compliance requirements.

How do I verify webhook signatures for BFL FLUX API delivery notifications?

Verify BFL FLUX API webhook signatures to validate the authenticity of delivery notifications. This security mechanism ensures your server only processes legitimate Ready responses for completed image generation jobs, preventing unauthorized requests from triggering downloads.