
Open Generation history in the Imagild API console, select the relevant key and choose Image, Video or All. Find the task using its identifier, model and creation time, then read its task status and billing state together. A filtered list helps locate an existing operation; it is not a complete statement of every change to your account balance.
Use the owning account. The console's history is an account-owner view, not a public endpoint for browsing other users' jobs or a substitute for your application's permission checks.
Key Takeaways
- Key and media filters narrow the records; reset them before deciding a task is missing.
- Refresh records reads stored history without starting another generation or forcing an upstream model check.
- Reserved, Consumed, Released and Not reserved describe different accounting states; the Points number needs that context.
Locate the record with the fewest assumptions
- Sign in to the account that owns the integration and open the API console.
- Expand Generation history under the keys table.
- Choose the intended key using its name and masked prefix.
- Set Task type to Image, Video or All as appropriate.
- Match the task identifier where available, then compare model and creation time.
- Use Load more records for earlier entries, keeping the selected filters in mind.
The key selector uses the keys loaded in the console. If an older key is absent from that selector, use Load older keys in the key-management area and check again. Key-list history and task-list pagination are separate controls.
Do not paste a full secret into a search field or support message. A key name and masked prefix are operational identifiers, not the credential needed to authenticate an application. Keep even these limited details within an appropriate audience.
Read task status beside the billing state
Each record identifies the media type, model, creation time, key name and prefix, task status, points and billing state. Use the task ID to connect it to the corresponding operation in your own application.
| Billing state | How to interpret the record | What not to infer |
|---|---|---|
| Reserved | Points remain committed to that operation | The job is complete or those points are already released |
| Consumed | The record reports completed generation usage | Every other wallet change belongs to this task |
| Released | The reservation was released | A cash purchase was refunded |
| Not reserved | The record does not report a reservation | The requested job succeeded for free |
The billing-state guide explains the lifecycle in more detail. A point amount shown next to Reserved is a commitment, while the same amount next to Consumed has a different meaning. Do not sum every displayed amount into a single completed-spend total.
Refresh a stored observation honestly
Choose Refresh records to reload the selected history. This view reads stored task information; it does not itself submit another paid task or force a fresh request to the model provider. An unresolved status may remain unresolved after a list refresh.
For example, a fictional operator finds a video task with the expected key and creation time, but its state is still unknown with points reserved. The correct record is “existing task located; outcome unresolved.” Refreshing the list three times does not create three charges, confirm failure or authorize a replacement.
If an integration needs a fresh task observation, follow the documented authenticated task-read workflow and its timing instructions. Keep the new observation separate from the previous stored state. Access failure and generation failure are different events.
Investigate an empty result before replacing work
Clear the key filter, set media to All and look for the known task ID again. Check whether you are using the intended account, whether the task was actually accepted through the API and whether earlier pages remain to be loaded. The API history view is not a promise to list every editor action or workbench-only project.
If the task is still missing, preserve the original submission reference and last received response. Do not submit the same prompt under a different key merely to make a new row appear. The support-packet guide lists useful sanitized evidence.
Turn a located task into a useful reconciliation record
In your own private record, pair the unique task ID with the observed time, key name or prefix, model, task status, points and billing state. Label this as your application record; the console does not promise a built-in CSV export or full account-ledger report.
Use one latest observation per task when calculating totals. The batch-reconciliation guide shows how to keep consumed and unresolved amounts separate. For actual media downloads, the owner-scoped export guide covers a different workflow: history rows do not contain prompts or private output links.
Sources and scope
Prepared from the current Imagild API-console implementation and published integration guides, checked October 30, 2026. The list exposes limited account-owned metadata; it does not reveal complete keys, prompts, source files or private result URLs. The example is hypothetical, and no paid generation or customer-history access was performed to write this guide.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. Report a correction.
Cover: AI-generated conceptual illustration; not an application screenshot, observed result, private account record or privacy guarantee.