Akool talking photo links expire in 7 days: what to archive

Akool's Talking Photo overview says the resources (image, video, voice) generated by its API are valid for 7 days and should be saved promptly. On Sume the generated media URLs are durable media.sume.com links that the docs say do not expire, so the archive step becomes a product choice, not a deadline.

Akool facts are from its overview page; Sume facts from Runs, read 2026-10-01.

What does the Akool page say about retention?

Two lines matter: the 7-day validity, and a best-practice note under result cleanup to save generated videos promptly. The same page lists video_status values 1 (in queue), 2 (processing), 3 (success) and 4 (failed), says to download the result URL at status 3, and offers a webhookUrl parameter plus a 720 or 1080 resolution choice.

How do the two compare?

What should I archive?

With a 7-day window, anything you will need after day 7 must be copied: the final video, and the source image and audio if you may regenerate. With Sume the docs note the URLs are public to anyone holding them, so copy the file only if you need per-customer access control or your own retention rules. Store the job id and the URL together either way.

How do callbacks differ?

Sume's webhook_url must be public HTTPS; localhost, private-network and non-HTTPS URLs are rejected. Delivery is terminal-only (job.completed, job.failed, job.canceled), with no progress callbacks, so keep status polling as a backup. Debugging steps are in debug Sume webhook delivery.