API Reference

The Fluxara API is job-oriented. Clients submit a processing request, inspect job state, and retrieve output artifacts after completion. API access is currently limited to approved beta environments.

Base URL

https://fluxara.net/api/v1

The current beta API uses a compact surface area and may evolve as the platform matures.

Authentication

API access is limited to approved beta users. Requests should include a bearer token in the Authorization header.

Authorization: Bearer <token>

Authentication format and token lifecycle may change during the beta period.

API flow

Status List Pipelines Create Job Check Job Read Outputs

Service status

Returns basic service-level status information for the current environment.

GET /status

Example request

curl -H "Authorization: Bearer <token>" \
  https://fluxara.net/api/v1/status

Example response

{
  "status": "ok",
  "service": "fluxara-core",
  "version": "0.9.3-beta",
  "environment": "closed-beta"
}

List pipelines

Returns the currently available pipeline identifiers in the active environment.

GET /pipelines

Example request

curl -H "Authorization: Bearer <token>" \
  https://fluxara.net/api/v1/pipelines

Example response

{
  "pipelines": [
    {
      "id": "text-to-image-basic",
      "type": "image",
      "status": "active"
    },
    {
      "id": "image-transform-standard",
      "type": "image",
      "status": "active"
    },
    {
      "id": "review-batch-a",
      "type": "batch",
      "status": "limited"
    }
  ]
}

Create job

Creates a new processing job using a selected pipeline, preset, and input payload.

POST /jobs

Example request

curl -X POST https://fluxara.net/api/v1/jobs \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "pipeline": "text-to-image-basic",
    "preset": "sdxl-cinematic-beta",
    "input": {
      "prompt": "cinematic rainy street at night, neon reflections, highly detailed"
    },
    "options": {
      "count": 2,
      "resolution": "1024x1024"
    }
  }'

Example response

{
  "job_id": "job_01HZX8A4QK1T",
  "status": "queued",
  "created_at": "2026-03-27T08:00:00Z"
}

Get job status

Returns the current execution state of a previously created job.

GET /jobs/{job_id}

Example request

curl -H "Authorization: Bearer <token>" \
  https://fluxara.net/api/v1/jobs/job_01HZX8A4QK1T

Example response

{
  "job_id": "job_01HZX8A4QK1T",
  "status": "running",
  "pipeline": "text-to-image-basic",
  "preset": "sdxl-cinematic-beta",
  "created_at": "2026-03-27T08:00:00Z",
  "updated_at": "2026-03-27T08:00:12Z"
}

List job outputs

Returns output artifacts and associated metadata for a completed job.

GET /jobs/{job_id}/outputs

Example request

curl -H "Authorization: Bearer <token>" \
  https://fluxara.net/api/v1/jobs/job_01HZX8A4QK1T/outputs

Example response

{
  "job_id": "job_01HZX8A4QK1T",
  "status": "completed",
  "outputs": [
    {
      "artifact_id": "art_01HZX8C2J9MX",
      "type": "image/png",
      "width": 1024,
      "height": 1024,
      "download_url": "/api/v1/artifacts/art_01HZX8C2J9MX"
    }
  ]
}

Download artifact

Retrieves a previously produced output artifact.

GET /artifacts/{artifact_id}

Example request

curl -L -H "Authorization: Bearer <token>" \
  https://fluxara.net/api/v1/artifacts/art_01HZX8C2J9MX \
  -o output.png

Authentication failure example

Unauthorized or unapproved environments may receive an access denial response.

GET /auth

Example response

{
  "error": "access_denied",
  "message": "closed beta environment"
}

Status values

queued

The job was accepted and is waiting for execution.

running

The job is currently being processed.

completed

The job finished successfully and outputs are available.

failed

The job could not be completed and no usable output was produced.

Error format

Error responses use a compact JSON structure.

{
  "error": {
    "code": "invalid_request",
    "message": "Preset is not available in the current environment."
  }
}

Operational notes

  • API availability is limited to approved beta users.
  • Request and response formats may change during beta.
  • Rate limits may vary by environment.
  • Artifact retention windows may differ across workspaces.

Design principles

Small surface area

The API stays intentionally compact during the beta period.

Job-oriented design

Execution is modeled as explicit jobs rather than implicit actions.

Artifact-first outputs

Completed jobs expose output files and metadata in a predictable way.

Beta flexibility

Formats may evolve as the platform matures.