Logs and retention
Every request is logged with its input, output, credits and timing, and kept for a fixed period.
Every submission, including rejected ones, is visible under Settings → API Logs with its request id, input, output, credits and timing. The same data is available programmatically through GET /v1/generations.
What is stored
- The request
inputwith prompts truncated to 2,000 characters. - Inline
data:images in your request are uploaded to our storage and the log stores the resulting URLs, not the base64 payload. - The
outputURLs, thecreditscharged, whether they were refunded, and how long the generation took. - The key that made the request, so a leaked key can be traced and revoked.
Retention
Completed and rejected request records become eligible for daily cleanup after 180 days. Pending generations and requests awaiting a billing review are retained until resolved. This cleanup removes request records; it does not delete generated files from your account library.
Content expires after 30 days
Download API results from API Logs before the expiry shown in request details. Expired input and output are hidden immediately; daily maintenance removes files and generation content. The request ID, status and credit history remain for the 180-day log period. Web generations are unaffected. See result retention for fields and timing.