Send Waiver Reminders

Chase the customers on a booking who still haven't signed their waivers. The waiver request is re-sent only to the unsigned — anyone who already signed is left alone. This is the same chase logic the scheduled waiver:send-reminders command runs, triggered for a single booking.

The supplier's settings (Settings → Notifications → Waivers & forms) apply: the feature must be switched on, and reminders stop once a customer reaches the attempt limit. A call sends now, without waiting for the automatic schedule; a second call within 15 minutes of the last reminder is refused.

Endpoint

POST /v1/bookings/{id}/waiver-reminders

Authentication

Requires an API key with the bookings:write scope.

Path Parameters

Parameter	Type	Description
id	integer	Booking ID

Response

Success (200 OK)

{
  "data": {
    "message": "Waiver reminder sent to customers who still haven't signed.",
    "pairs_chased": 2
  },
  "meta": {
    "request_id": "req_abc123",
    "timestamp": "2026-07-19T09:00:00+00:00"
  }
}

pairs_chased counts the customer × waiver pairs the reminder covered.

No reminder due (422)

{
  "error": {
    "code": "no_reminder_sent",
    "message": "No waiver reminder is due yet."
  }
}

Returned when the feature is switched off, the booking isn't live, every waiver is already signed, the attempt limit is reached, or a reminder went out in the last 15 minutes.

Example Request

curl -X POST "https://app.equipdash.com/api/v1/bookings/123/waiver-reminders" \
  -H "Authorization: Bearer YOUR_API_KEY"

Errors

Status	Code	Description
401	authentication_required	No API key provided
401	invalid_api_key	Invalid API key
403	insufficient_scope	API key lacks bookings:write scope
403	forbidden	Booking belongs to another supplier
404	not_found	Booking not found
422	DRAFT_NOT_CONFIRMED	The booking is a draft. Confirm it before sending
422	no_reminder_sent	Feature off, not live, all signed, limit reached, or a reminder went out in the last 15 minutes