estudjo API: Archive a Scene via DELETE /scenes/{id}

Archiving a scene removes it from GET /scenes and prevents it from being used in new generations. This is a soft delete — the scene data is retained internally but is permanently inaccessible through the API.

Endpoint

string

required

Your API key.

DELETE https://v1.api.estudjo.com/scenes/{scene_id}

Path Parameters

string

required

UUID of the user-created scene to archive.

There is no restore endpoint. Once a scene is archived, it cannot be recovered. Create a new scene via POST /scenes if you need to recreate it.

Example Request

curl -X DELETE https://v1.api.estudjo.com/scenes/7c1e2f4a-9b3d-4e5f-8a6b-1c2d3e4f5a6b \
  -H 'X-Api-Key: YOUR_API_KEY'

Response

200 — Success

{ "success": true, "data": { "status": "archived" } }

string

Always archived on a successful delete.

What Archiving Affects

After a scene is archived, the following changes take effect immediately across the API:

Endpoint	Behaviour after archiving
`GET /scenes`	Scene no longer appears in results.
`GET /scenes/{scene_id}`	Returns `404 not_found`.
`POST /generate` (with this scene_id)	Returns `not_found`.
`PUT /scenes/{scene_id}`	Returns `404 not_found`.

Errors

Code	HTTP	Cause
`not_found`	404	The scene doesn’t exist, belongs to another account, is predefined, is already archived, or `scene_id` is not a valid UUID. All cases are intentionally indistinguishable.

Health

API Keys

Wallet

Generations

Scenes

estudjo API: Archive a Scene via DELETE /scenes/{id}

Endpoint

Path Parameters

Example Request

Response

200 — Success

What Archiving Affects

Errors

​Endpoint

​Path Parameters

​Example Request

​Response

​200 — Success

​What Archiving Affects

​Errors

Endpoint

Path Parameters

Example Request

Response

200 — Success

What Archiving Affects

Errors