Archive and republish

Archive removes a video from feeds, search, and recommendations without losing the asset or any history. Republish puts it back. Use archive for embargo windows, content rotation, or temporary takedowns during reviews. Use DELETE only for permanent removal.

Archive

curl -X POST https://api.myeden.me/v1/videos/vid_a7Kp9m.../archive \
  -H "Authorization: Bearer $EDEN_API_KEY"

Response:

{ "id": "vid_a7Kp9m...", "status": "archived" }

After archiving:

The video is no longer returned in any feed
Search excludes it
Recommendations re-rank to remove it
Direct playback links continue to work for ~5 minutes (CDN cache), then return 404 to viewers
The underlying Mux asset and captions are preserved

Republish

curl -X POST https://api.myeden.me/v1/videos/vid_a7Kp9m.../republish \
  -H "Authorization: Bearer $EDEN_API_KEY"

Response:

{ "id": "vid_a7Kp9m...", "status": "public" }

Republishing re-indexes the video across feeds, search, and recommendations within ~60 seconds.

Archiving a video that’s still processing

You can call archive on a video that’s still processing. The archive intent is queued, and the video will be created in an archived state when processing completes — meaning it never appears in feeds. Useful if you realize mid-pipeline that the content shouldn’t be live. Response (queued archive):

{
  "id": "vid_a7Kp9m...",
  "status": "archive_queued",
  "message": "Video is still processing. It will be archived when ready."
}

Archive vs delete

	Archive	Delete
Reversible	Yes (`republish`)	No
Mux asset preserved	Yes	No
Captions preserved	Yes	No
Use for	Embargoes, rotation, temporary takedowns	Permanent removal

Getting started

Working with videos

Archive

Republish

Archiving a video that’s still processing

Archive vs delete

​Archive

​Republish

​Archiving a video that’s still processing

​Archive vs delete

Archive

Republish

Archiving a video that’s still processing

Archive vs delete