Notification Handlers: Delete
Straightforward guide for developers on how to delete an existing notification handler using the API, including the necessary headers and the expected behavior of the response.
Endpoint
DELETE /api/notification-handlers/{notification_handler_id}
/api/notification-handlers/{notification_handler_id}Delete an existing notification handler by its unique identifier.
Request
HTTP Request
DELETE https://uptimekeep.com/api/notification-handlers/{notification_handler_id}Replace {notification_handler_id} with the ID of the notification handler you wish to delete.
Headers
Authorization
String
Bearer token for API authentication.
Example of a request:
curl --request DELETE \
--url 'https://uptimekeep.com/api/notification-handlers/{notification_handler_id}' \
--header 'Authorization: Bearer {api_key}'Response
A successful request will result in the deletion of the specified notification handler. Typically, a 204 No Content status code is returned, indicating that the operation was successful and no content is returned in the response body.
Errors
If the request fails, the API will return an error message with an appropriate HTTP status code, such as 404 Not Found if the notification handler ID does not exist.
Last updated