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.

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.
| Item | Higgsfield | Sume `/v1/videos` |
|---|---|---|
| Result field | video.url on a completed request | unsigned_urls[0] on a completed job |
| Auth to download | Not described on the retention page | API key on the content endpoint |
| Stated retention | At least seven days | No expiry stated on the video page |
| Advice | Download for long-term storage | Download 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
- Higgsfield polling: 2 to 10 seconds with jitter, vs Sume
Higgsfield says start polling at 2 seconds, grow to 10, add jitter. Sume's video docs poll every 30 seconds and honor next_poll_after_seconds. How to pick.
- Higgsfield statuses: nsfw and canceled mapped to Sume job states
Higgsfield returns queued, in_progress, completed, failed, nsfw or canceled. How each maps to Sume's video and job statuses, including cancelled vs canceled.
- Higgsfield upload URL: 1 hour, MP4 and WAV. Sume takes public URLs
Higgsfield inputs go through a presigned upload that expires in one hour. Sume has no upload step: pass public HTTPS URLs in frame_images or input_references.
- Higgsfield webhook retries: two hours vs Sume's ten attempts
Higgsfield retries 5xx for up to two hours and wants a reply in ten seconds. Sume makes 10 attempts, 30 seconds apart, then lets you redeliver by hand.
Written by Sume