Set SSL Expiration Reminder

Create an automated reminder for an SSL certificate by providing the associated resource_id in the path and specifying reminder settings in the request body. This ensures your team is notified before the certificate expires, helping prevent service disruptions and trust issues caused by lapsed security credentials.

You can configure the number of days in advance the reminder should trigger (e.g., 7 or 14 days before the expiration date), giving your team enough time to take renewal actions.

Common use cases:
  • SSL certificate expiration tracking — Set up proactive reminders to avoid missing critical renewal deadlines for HTTPS-enabled services.
  • Security compliance — Ensure SSL certificates are renewed in a timely manner to maintain compliance with security standards.
  • Operational continuity — Prevent last-minute renewals or outages due to expired SSL certs across monitored services.

You can view and manage existing reminders via the SSL Settings page.

Authorization: Bearer YOUR_TOKEN

Path Parameters
  • id string
    The unique service ID for which the SSL reminder will be created.
    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.post(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).