Versioned routes
Public API paths live under /v1, with request and response shapes recorded in OpenAPI.
Developer surface
Build against the versioned FluxVision API contract.
The public OpenAPI document is the canonical machine-readable contract for FluxVision v1 endpoints, schemas, authentication requirements, and error envelopes.
Start with the contract
Download the current OpenAPI YAML. Except for documented health endpoints, API requests require an authenticated account session or an authorized API key. Keep keys out of client bundles and public repositories.
Integration guarantees
Request IDs
Error responses include a request identifier that can be matched to the response header for support and tracing.
Idempotency
Documented write operations use idempotency boundaries so safe retries do not create duplicate work.
Private by default
API responses are not publicly cached, and workspace authorization is enforced for owned resources.
Contract before examples
Authentication, required headers, status codes, and schema fields can change as the versioned contract evolves. Generate clients and validation from the OpenAPI document instead of copying an undocumented request example.