Delete SSL Reminder
Permanently remove an SSL certificate expiration reminder by specifying the related service_id in the path. Once deleted, no future alerts will be sent for the SSL certificate tied to that service, giving you full control over which reminders remain active.

This is useful when a certificate is no longer in use, has been renewed with automated management, or when you're reorganizing SSL tracking across multiple services.

Common scenarios:
  • Certificate deprecation — Remove reminders tied to legacy services or certificates no longer being monitored.
  • Switching to automated renewals — Eliminate manual reminders for certs that are now managed by tools like Let’s Encrypt or cloud providers.
  • Reducing noise — Clean up irrelevant or duplicate reminders to keep your SSL alerting streamlined.

To modify a reminder instead of deleting it, use the Update SSL Reminder endpoint.
To review current SSL reminder configurations, visit the SSL Settings page.

Authorization: Bearer YOUR_TOKEN



Expected Behavior:

  • On success, the SSL reminder will be deleted, and a confirmation message will be returned.
  • If the request is unauthorized or the provided service ID is invalid, an error message will be returned, specifying the issue.
Path Parameters
  • id string
    The unique service ID for which the SSL reminder will be deleted.
    Example: 'c03b02ec-244f-4d2c-8f68-3910071ed5c8'
JavaScript
Response codes
const axios = require('axios');

const url = 'https://resource-cmd.api.pinghome.io/v1/ssl/reminder/c03b02ec-244f-4d2c-8f68-3910071ed5c8';

axios.delete(url, {
  headers: {
    'Authorization': 'Bearer YOUR_TOKEN'
  }
})
.then(response => {
  console.log(response.data);
})
.catch(error => {
  console.error(error);
});
ResponseThis section is used to view the possible HTTP response codes returned by the API. These codes indicate the status of a request, such as 201 (Created), 401 (Unauthorized), 409 (Conflict), or 422 (Unprocessable Entity).