Update notification settings (removed)
curl --request PUT \
--url https://statusstack.com/api/v1/notifications \
--header 'Authorization: Bearer <token>'const options = {method: 'PUT', headers: {Authorization: 'Bearer <token>'}};
fetch('https://statusstack.com/api/v1/notifications', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://statusstack.com/api/v1/notifications"
headers = {"Authorization": "Bearer <token>"}
response = requests.put(url, headers=headers)
print(response.text){
"message": "<string>"
}Notifications
Update notification settings (removed)
deprecated
No longer supported. Notification settings were never persisted by this endpoint; it now answers 410. Manage notification rules in the dashboard.
PUT
/
v1
/
notifications
Update notification settings (removed)
curl --request PUT \
--url https://statusstack.com/api/v1/notifications \
--header 'Authorization: Bearer <token>'const options = {method: 'PUT', headers: {Authorization: 'Bearer <token>'}};
fetch('https://statusstack.com/api/v1/notifications', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://statusstack.com/api/v1/notifications"
headers = {"Authorization": "Bearer <token>"}
response = requests.put(url, headers=headers)
print(response.text){
"message": "<string>"
}Authorizations
StatusStack authenticates requests with API keys, created via the dashboard with granular permissions (read, write, delete, admin, *).
API keys support version compatibility:
- v1 keys: Can only access v1 endpoints
- v2 keys: Can access both v1 and v2 endpoints
Available permissions:
read: View resources (GET requests)write: Create and update resources (POST, PUT requests)delete: Delete resources (DELETE requests)admin: Administrative access to all resources*: Wildcard permission (all actions allowed)
Response
410 - application/json
Endpoint removed
Was this page helpful?

