Higgsfield output URLs last at least 7 days: copy files out

Higgsfield keeps generated output for at least seven days and may remove it later. Where Sume serves a finished video, and why to copy it to your own storage.

4 min readSume
All posts

Higgsfield says generated output is accessible for at least seven days after creation and may be removed after that, so you should download what you want to keep. Sume's /v1/videos route returns a content URL for a completed job, and the docs read for this post do not name an expiry for it, so the safe habit is the same: copy the file to storage you control.

What Higgsfield promises

The lifecycle page says output URLs are retained for at least seven days, and the FAQ repeats a minimum of seven days from creation. Both say to move media to your own storage for longer. Note the wording: a minimum, not a promise, and the page does not say what happens on day eight.

What Sume returns

A completed /v1/videos job returns unsigned_urls, each pointing at GET /v1/videos/{jobId}/content?index=0. You call it with your API key in the Authorization header, and index defaults to 0 for models that return several outputs. The jobs guide adds that public events do not expose raw provider task ids or raw provider URLs, so there is no provider link to rely on.

Where the finished video lives, read 2026-10-02
ItemHiggsfieldSume `/v1/videos`
Result fieldvideo.url on a completed requestunsigned_urls[0] on a completed job
Auth to downloadNot described on the retention pageAPI key on the content endpoint
Stated retentionAt least seven daysNo expiry stated on the video page
AdviceDownload for long-term storageDownload what you need to keep

Do not mix the surfaces

Sume has other surfaces with different media rules. Format runs and Agent Completions return media on media.sume.com URLs that do not expire, as covered in do Sume video URLs expire. Do not assume that holds for the /v1/videos content endpoint, and read each route's own page.

A safe habit

Whatever the retention window is, the same three steps keep you safe.

  • Download as soon as the status is completed, not when a customer asks for it.
  • Store the job id next to the saved file so you can find the usage row later.
  • Keep the saved file, not the URL, as your system of record.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume