APIMART Growth evidence. WAN 2.7 Image facts were checked on 2026-09-02. CTA links are attributed to this exact GitHub guide.
WAN 2.7 Image API Limits: Resolution, Inputs and Request Boundaries
APIMART serves WAN 2.7 Image 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
- wan2.7-image supports output up to 2K; the Pro text-to-image route supports up to 4K.
- Editing and sequential-generation workflows support output up to 2K.
- The endpoint accepts up to 9 reference images, each up to 20 MB and 240 to 8000 pixels.
- Supported image dimensions must remain between aspect ratios of 1:8 and 8:1.
- The standard route supports n from 1 to 4; sequential generation can produce up to 12 images.
- The documentation says failed requests are not charged and billing applies per successful image.
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 WAN 2.7 Image?
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 WAN 2.7 Image 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
Machine-readable schema source
The eventual APIMART CMS page should emit these JSON-LD objects.
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "WAN 2.7 Image API Limits: Resolution, Inputs and Request Boundaries",
"mainEntityOfPage": "https://apimart.ai/blog/wan-2-7-image-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 WAN 2.7 Image?",
"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."
}
}
]
}
]