4oImageApi.io keeps images for only 14 days: asynchronous generation should end with archiving
Teams integrating 4oImageApi.io into a design backend should separate task success from asset delivery: track status by taskId and save results to storage they manage within the 14-day retention period. A callback can notify you of completion; it cannot replace file archiving.
Once a design backend is connected to 4oImageApi.io, can you close a task as soon as a generation-complete notification arrives? Not if the image is needed for next month's campaign. The official documentation says generated images are kept for only 14 days. Asynchronous generation lets the backend handle “submitting the request” and “obtaining the result” separately, but the team still needs to add an archiving step of its own.
This is a documentation-based analysis of an internal asset-generation task, not an actual API test. Suppose a designer requests an image for a campaign. The developer's deliverable is an image that can be reopened in the team's own asset library, not merely a successful task status on the server.
Callbacks announce completion; status queries help confirm the result
The documentation says that a POST notification is sent to the specified callback URL when a task completes. The details endpoint can use taskId to retrieve generation status, parameters and results. During integration, associate the image request with its taskId in your own task record so that later queries can be traced back to the original request.
The interface should also distinguish “generating” from “ready for the designer to inspect.” The documented statuses include GENERATING, SUCCESS, CREATE_TASK_FAILED and GENERATE_FAILED. Check the status and result after receiving a notification before deciding whether to keep waiting, handle a failure or inspect the image. Do not treat every notification as proof that a usable asset has arrived.
If you use polling, the documentation sets a maximum of 3 queries per second per task. This is a query limit, not a recommended frequency or a promise of generating 3 images per second. Set the interval according to the waiting experience you want to provide, and stop repeated queries when the task reaches a terminal state. Status monitoring should not be confused with image-generation throughput.
The 14-day retention period makes archiving part of integration
For an image that will not be used until next month, merely recording the provider's result URL in a spreadsheet is not a sound enough plan. Since images expire after 14 days, save the selected result to storage you manage within that period, then write the internal asset location back to the task record. Archiving is a responsibility your integration must implement. “Callback support” does not imply that the product will store files permanently for you.
Acceptance checks can follow that same request: confirm that the result opens, the image meets the design requirements and the internal copy can be read independently, then mark the task as delivered. If generation succeeds but archiving fails, retain separate states so that saving can be completed later, rather than leading the designer to believe the asset is already in the library. This is a proposed acceptance design; its actual operation has not been tested here.
For an internal experiment that needs only a temporary preview, the team can accept short-lived results, but it should still tell users about the retention boundary. Once assets need long-term reuse, establish the storage location and responsibility for handling failures before expanding the integration. The asynchronous capability of 4oImageApi.io provides a way to handle waiting and notifications separately; the team's delivery standard should be a file it can continue to retrieve.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:docs.4oimageapi.io