Skip to main content
Every generation request stores the files you send and the files it produces. You decide how long they are kept: seven days by default, or as little as one hour. You can also delete a finished request at any time.

Retention periods

Retention counts from the moment the request finishes (completed, failed, nsfw or canceled), so a long generation does not eat into the time you have to download its result. The period is fixed when the request is created: changing the account retention later does not affect existing requests.

Set retention for a request

Send Hf-Expires-After with the number of seconds to keep the request after it finishes:
The response confirms the period that applies:
  • A value below 3600 or above your account retention returns 422 Unprocessable Entity.
  • The header is part of the Idempotency-Key fingerprint: retry with the same value.
  • The header applies to generation requests for the models in the Model API reference.

When data expires

Once a request finishes, the status response and the webhook include expires_at, the time after which its data is deleted:
Download the output before expires_at. After it, output URLs stop working. The status endpoint keeps returning the request with its status, but the files are gone.
With retention shorter than the webhook retry window, a delivery to an endpoint that is down for longer than the retention period is not retried after the data is deleted. Keep polling the status endpoint as a fallback.

Delete a request now

Delete a finished request’s data immediately, regardless of its retention:

What is deleted

When a request expires with retention shorter than seven days, or when you delete it: With the default seven-day retention, the request’s files are deleted after seven days; the prompt and parameters stay with the request record. Use a shorter retention or DELETE to remove them too. Billing records stay, so usage reports and invoices are not affected by deletion. Files you upload with file uploads, and copies of inputs that Higgsfield prepares for reuse across requests, are stored independently of a single request and are deleted within seven days. Requests processed by third-party model providers are also subject to the provider’s own data policy.