How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Flux Editing API

Endpoints for submitting image editing requests using FLUX.1 Kontext models. Accepts an input image and a text instruction to produce a transformed output image.

Flux Editing API is one of 3 APIs that Flux publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Editing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, authentication docs, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://api.bfl.ai/v1.

2 operations 2 paths 4 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://api.bfl.ai/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Flux Editing API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — API key from the Black Forest Labs developer portal. Pass in the X-Key header for all authenticated requests.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Editing 2

Endpoints for submitting image editing requests using FLUX.1 Kontext models. Accepts an input image and a text instruction to produce a transformed output image.

POST
/flux-kontext-pro
Edit image with FLUX.1 Kontext [pro]
editImageKontextPro body → 200400401422
POST
/flux-kontext-max
Edit image with FLUX.1 Kontext [max]
editImageKontextMax body → 200400401422

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are KontextEditRequest (8 properties), ErrorResponse (2 properties), TaskResponse (2 properties), ValidationErrorResponse (1 property). Each schema is shown below with its type and property counts.

TaskResponse
object
Response returned when an image editing task is accepted. Contains the task ID for polling.
2 properties
KontextEditRequest
object
Request body for FLUX.1 Kontext image editing. Requires both an input image (base64-encoded) and a text prompt describing the desired edit to apply.
8 properties 2 required
ValidationErrorResponse
object
Validation error response when the request body fails validation.
1 property
ErrorResponse
object
Error response.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flux-editing-api-openapi.yml Raw ↑

Other APIs Flux publishes across the network.

Flux Generation API
Flux Results API
Where this information came from

This is an independent, third-party profile of Flux Editing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.