
An empty Imagild output_url immediately after submission usually means no successful output has been reported yet. The generation response is a task record, not a synchronous array of image URLs. Read data.status first; only a succeeded task exposes its authenticated content route.
The Imagild API console describes this submit-then-read workflow. Fix the application's output gate before changing the model, prompt or image size; those changes would create a different generation rather than make the existing result arrive.
Key Takeaways
- Null output is expected while a task has no reported successful result.
- Enable download only when status is succeeded and the output route is valid.
- A private content URL still requires authentication; it is not a public preview address.
Decide from status, not from an empty image element
Use these branches when a task card has no picture:
| Task observation | Interpretation | Next step |
|---|---|---|
| Nonfinal working state with null output | Generation has no reported result yet | Schedule another bounded GET |
| Failed with null output | No successful result is reported | Show error and inspect usage |
| Unknown with null output | Outcome is unresolved | Retain identity for review |
| Succeeded with an output route | Result can be requested | Download authenticated bytes |
| Succeeded but missing output route | Response contradicts the expected contract | Preserve diagnostics and investigate |
Do not make output_url == null alone trigger a retry. That condition appears in both normal waiting and unsuccessful outcomes.
Runware's task-polling guide also separates an initial acknowledgment from available results. Its partial-result arrays and delivery options are different from the current Imagild record, so do not copy their parser into this integration.
Resolve the returned route against the website origin
For a successful task, Imagild returns a relative path such as /api/relay/v1/tasks/{id}/content. Appending that path to an already versioned base string can duplicate the prefix. Resolve an absolute-path reference against the origin instead.
This server-side helper is an output gate for a task whose ID has already been checked against your owned operation record. It does not submit or poll work:
function contentUrlForSucceededTask(task) {
if (task.status !== "succeeded") return null;
if (typeof task.output_url !== "string" || !task.output_url) {
throw new Error("Succeeded task has no output route");
}
const url = new URL(task.output_url, "https://imagild.com");
const expected = "/api/relay/v1/tasks/" + task.id + "/content";
if (url.origin !== "https://imagild.com" ||
url.pathname !== expected || url.search || url.hash) {
throw new Error("Unexpected output route");
}
return url;
}
Checking the destination before attaching an Authorization header also avoids sending your secret to an unexpected host. Keep that key out of browser scripts and query strings.
Distinguish result availability from browser display
Your backend can request the validated content URL with its Bearer key. The account must still have active membership. A 401 or membership-related 403 during this request is an access issue; it does not mean another paid image should be generated.
After a successful media response, inspect Content-Type and decode the bytes. Images may be PNG, JPEG or WebP. If the saved file contains HTML or JSON, review the download payload diagnostic before assigning an image extension.
A browser's blank video card is another layer: it may need a poster even when a video file exists. The poster-versus-first-frame guide explains that display distinction. Do not infer an unfinished API task only from the thumbnail.
Verify the gate before a paid integration test
Create local fixtures for queued with null output, failed with null output, unknown with null output, and succeeded with a valid relative route. Assert that only the final case enables content retrieval.
Then inject an external hostname and a succeeded response lacking its route. The helper should reject both without exposing credentials or resubmitting generation. Confirm that the failed fixture leads to the appropriate next-action review.
This small gate makes the product feel more dependable: users see waiting, review, or downloadable media for the right reason, instead of a broken image icon that invites another charge.
Related tasks
- Why Does My Downloaded Image Open as a Web Page?
- Why Does a Video Card Show a Black Image Before Playback?
- What Should You Check Before Retrying a Failed Image or Video Job?
Sources and scope
- Imagild API console and integration guide: Current Imagild entry point, active-member access, asynchronous task reading and authenticated output contract; implementation facts cross-checked in lib/relay and the 2026-10-28 claims manifest.
- Runware Task Polling: General asynchronous acknowledgment/result separation and spaced polling. Runware-specific task shapes, partial results, SDKs and webhooks are not attributed to Imagild.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.