Restore an asset you archived
POST
/v1/assets/{public_id}/restore
const url = 'https://example.com/v1/assets/example/restore';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/assets/example/restore \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”public_id
required
Public Id
string
Header Parameters
Section titled “Header Parameters”Responses
Section titled “Responses”Successful Response
Media typeapplication/json
AssetLifecycleResponse
The outcome of archiving or restoring one asset.
Three fields on purpose. A client asking to hide an asset needs to know that it is hidden and which library tab it came from — not the row’s owner columns, provenance metadata, or storage key.
object
public_id
required
Public Id
string
status
required
Status
active | archived — the status after the change.
string
kind
required
Kind
The asset’s kind, so you can route it back to the right library view.
string
Examplegenerated
{ "public_id": "example", "status": "example", "kind": "example"}Validation Error
Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationErrorobject
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example" } ]}