Update SSL Reminder
Update the settings of an existing SSL certificate expiration reminder by specifying the associated resource_id in the path and submitting new reminder details in the request body. This allows you to adjust how far in advance your team is alerted about upcoming certificate expirations.

You can change the number of days before the expiration date when the reminder should trigger (e.g., updating a 14-day reminder to 7 days) without needing to recreate the reminder.

Use cases:
  • Adjusting lead time — Modify when reminders are sent to better align with internal workflows or vendor renewal cycles.
  • Optimizing alert timing — Shorten or extend the reminder window based on how quickly your team can renew certificates.
  • Ongoing SSL tracking — Maintain accurate and up-to-date reminder schedules across all SSL-monitored services.

To review existing configurations, visit the SSL Settings page.

Authorization: Bearer YOUR_TOKEN



Expected Behavior:

  • On success, the SSL reminder will be updated, 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 updated.
    Example: 'c03b02ec-244f-4d2c-8f68-3910071ed5c8'
Request Body Parameters
  • days_before array of integers
    An array of integers representing how many days before the SSL certificate expiration the reminder should be triggered.
    Example: [1]
JavaScript
Response codes
const axios = require('axios');

const url = 'https://resource-cmd.api.pinghome.io/v1/ssl/reminder/c03b02ec-244f-4d2c-8f68-3910071ed5c8';
const data = { days_before: [1] };

axios.put(url, data, {
  headers: {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
  }
})
.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).