Delete an exposure
curl --request DELETE \
--url https://api.storiza.store/apps/{id}/exposures/{exposureId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.storiza.store/apps/{id}/exposures/{exposureId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.storiza.store/apps/{id}/exposures/{exposureId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"message": "Exposure deleted",
"data": {
"ok": true
}
}App domains
Delete an exposure
Remove a domain you added.
Managed exposures are refused — they are the app’s own way in, and deleting one would strand it. Disable it instead with PATCH /apps/{id}/exposures/{exposureId}.
The container keeps its current routing until the app is next started, because it is built from these rows at start.
Required API key permission: null
DELETE
/
apps
/
{id}
/
exposures
/
{exposureId}
Delete an exposure
curl --request DELETE \
--url https://api.storiza.store/apps/{id}/exposures/{exposureId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.storiza.store/apps/{id}/exposures/{exposureId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.storiza.store/apps/{id}/exposures/{exposureId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text){
"success": true,
"message": "Exposure deleted",
"data": {
"ok": true
}
}Authorizations
An API key from the Storiza dashboard (API & Integrations), sent as Authorization: Bearer stz_….
Was this page helpful?