Read booking reminder settings

GET /api/v1/booking-reminder-settings

Read defaults used by new bookings only.

Authorization

Use an organization-bound API key. Owner/admin only. The key acts with its bearer’s current permissions, and never accepts an organization or actor in the body.

Example

curl -X GET 'https://www.cohorte.io/api/v1/booking-reminder-settings' \
  -H 'x-api-key: YOUR_API_KEY'

Response

200 returns the result. Invalid input is refused; missing authentication returns 401, insufficient permission 403, and inaccessible resources 404. Provider failures never imply successful synchronization.

Response fields

enabled, allowLateReschedule and steps with delayMinutes, subject and body.

Example response

{
  "data": {
    "enabled": true,
    "allowLateReschedule": false,
    "steps": [
      {
        "delayMinutes": 1440,
        "subject": "Your appointment",
        "body": "Please confirm."
      },
      {
        "delayMinutes": 120,
        "subject": "Your appointment",
        "body": "Please confirm."
      }
    ]
  },
  "success": true,
  "correlationId": "33333333-3333-4333-8333-333333333333"
}

Notes

Allowed template variables: name, date, time, timezone, closer, meetingUrl, enclosed in double braces. Up to eight distinct delays, between one minute and30days. No late catch-up. A same-schedule confirmation in the preceding24hours suppresses a due automatic request; older confirmation may prompt again. Public late rescheduling is disabled by default within24hours; enabled allows it until start. Operators remain exempt.

Related

• Booking details
• Booking email
• Reminder settings