APIMART Growth evidence. FLUX.2 facts were checked on 2026-09-02. CTA links are attributed to this exact GitHub guide.

FLUX.2 API Limits: Resolution, Inputs and Request Boundaries

APIMART serves FLUX.2 through POST /v1/images/generations. The current documentation describes an asynchronous submit-and-poll workflow. The boundaries below were checked on September 2, 2026.

Verified boundaries

• Use the exact model ID flux-2-flex or flux-2-pro; FLUX.2 is a family label.
• The current endpoint documentation lists 1K and 2K output-resolution controls.
• The route lists 7 supported aspect ratios.
• Image editing accepts up to 8 reference-image URLs; base64 reference input is not supported.
• Generation is asynchronous and successful submission returns task_id.
• Completed result URLs are documented as available for 24 hours, so production systems must copy them promptly.

Minimal integration rule

Send the documented model ID, required prompt and only compatible optional inputs. Persist the returned task_id, implement bounded polling and backoff, and keep 400, 401, 402, 429 and 5xx responses out of completed-output metrics.

FAQ

Which endpoint serves FLUX.2?

Use POST /v1/images/generations with the documented model ID and Bearer authentication.

Is processing synchronous?

No. A successful submission returns a task ID that must be polled for completion.

What is the first production safeguard?

Validate model ID, quantity or duration, resolution and input combinations before submission.

Can documented limits change?

Yes. Treat the live endpoint documentation as the source of truth and version your request profile.

Should a submitted task be counted as completed output?

No. Count success only after the task endpoint reports a completed result.

Try FLUX.2 on APIMART

Open the attributed model page or review current APIMART pricing.

Sources and disclosure

Technical source: APIMART endpoint documentation, checked September 2, 2026. APIMART operates the gateway; limits may change.

APIMART links for this guide

• Open FLUX.2 on APIMART
• Review current APIMART pricing

Machine-readable schema source

The eventual APIMART CMS page should emit these JSON-LD objects.

[
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "FLUX.2 API Limits: Resolution, Inputs and Request Boundaries",
    "mainEntityOfPage": "https://apimart.ai/blog/flux-2-api-limits-resolution-inputs",
    "dateModified": "2026-09-02",
    "author": {
      "@type": "Organization",
      "name": "APIMART"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Which endpoint serves FLUX.2?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Use `POST /v1/images/generations` with the documented model ID and Bearer authentication."
        }
      },
      {
        "@type": "Question",
        "name": "Is processing synchronous?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. A successful submission returns a task ID that must be polled for completion."
        }
      },
      {
        "@type": "Question",
        "name": "What is the first production safeguard?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Validate model ID, quantity or duration, resolution and input combinations before submission."
        }
      },
      {
        "@type": "Question",
        "name": "Can documented limits change?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Treat the live endpoint documentation as the source of truth and version your request profile."
        }
      },
      {
        "@type": "Question",
        "name": "Should a submitted task be counted as completed output?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. Count success only after the task endpoint reports a completed result."
        }
      }
    ]
  }
]