Update TLD Reminder

Update the configuration of an existing TLD (Top-Level Domain) reminder by specifying the resource_id in the path and submitting the updated reminder details in the request body. This allows you to fine-tune when reminder notifications are sent to better align with current domain management timelines.

You can update the number of days before the event when the reminder should be triggered (e.g., change a 7-day reminder to 3 days) — all without needing to recreate it.

Use cases include:
  • Adjusting timing — Modify the reminder trigger window to match updated domain renewal or review policies.
  • Ongoing maintenance — Keep reminder settings aligned with internal workflows as service or ownership structures change.

To review current domain configurations and linked reminders, visit the TLD Settings page.

Authorization: Bearer YOUR_TOKEN

Path Parameters
  • id string
    The unique service ID for which the TLD 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 event the reminder should be triggered.
    Example: [1, 3, 7]
JavaScript
Response codes
const axios = require('axios');

const url = 'https://resource-cmd.api.pinghome.io/v1/{id}/tld/reminder';
const data = { days_before: [1, 3, 7] };

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).