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

Z Image Turbo API Limits: Resolution, Inputs and Request Boundaries

APIMART serves Z Image Turbo 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

• A request returns an asynchronous task_id and generates exactly one image; n is not supported.
• The prompt limit is 800 characters.
• Resolution supports 1K and 2K tiers.
• Aspect ratios are 1:1, 4:3, 3:4, 16:9, 9:16, 3:2 and 2:3.
• prompt_extend defaults to false and can increase cost when enabled.
• The endpoint documentation says billing is per successfully generated image and failed generations are not charged.

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 Z Image Turbo?

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 Z Image Turbo 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 Z Image Turbo 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": "Z Image Turbo API Limits: Resolution, Inputs and Request Boundaries",
    "mainEntityOfPage": "https://apimart.ai/blog/z-image-turbo-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 Z Image Turbo?",
        "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."
        }
      }
    ]
  }
]