Restart an app
curl --request POST \
--url https://api.storiza.store/apps/{id}/lifecycle/restart \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.storiza.store/apps/{id}/lifecycle/restart', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.storiza.store/apps/{id}/lifecycle/restart"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"message": "Done",
"data": {}
}App lifecycle & console
Restart an app
Stop then start, going through exactly the same path as any other start — there is no separate restart route through the agent. It therefore re-resolves the image tag and rebuilds the container from stored rows, which is the point: a restart can never produce a container that a fresh start would not.
Required API key permission: apps:write
POST
/
apps
/
{id}
/
lifecycle
/
restart
Restart an app
curl --request POST \
--url https://api.storiza.store/apps/{id}/lifecycle/restart \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.storiza.store/apps/{id}/lifecycle/restart', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.storiza.store/apps/{id}/lifecycle/restart"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"message": "Done",
"data": {}
}Authorizations
An API key from the Storiza dashboard (API & Integrations), sent as Authorization: Bearer stz_….
Path Parameters
Minimum string length:
1Was this page helpful?