Consent Tracking

Track who still needs to sign a waiver or form, see the full per-participant timeline (requested, opened, each reminder with delivery status, signed, counter-signed), and chase the unsigned — for one person, one booking, or many bookings at once.

All endpoints read the same resolver the EquipDash portal uses, so the API can never disagree with the Consent tracker screen or the booking's Consents card.

Consent tracker

Every upcoming live booking that still has an outstanding consent, soonest booking first.

GET /v1/consent-tracker

Requires the bookings:read scope.

Query Parameters

Parameter	Type	Description
days	integer	Only bookings starting within the next N days
date_from	date (YYYY-MM-DD)	Booking-date window start (supplier-local day). The tracker never shows past bookings regardless of the range.
date_to	date (YYYY-MM-DD)	Booking-date window end (supplier-local day)
form_id	integer	Only outstanding signatures for this form
only	string	nobody_signed or chase_exhausted
search	string	Booking id, customer or group name
limit	integer	Max rows per page (default 100, max 200)
offset	integer	Rows to skip before the page starts (default 0). Page with limit + offset until you have total_count rows.

Response (200 OK)

{
  "data": {
    "bookings": [
      {
        "booking_id": 123,
        "display_name": "Jane Doe",
        "booking_type": "rental",
        "start_date": "2026-08-12T16:00:00.000000Z",
        "signed": 1,
        "required": 3,
        "outstanding": 2,
        "opened_not_signed": 1,
        "next_reminder_at": "2026-08-09T14:00:00.000000Z",
        "next_attempt_number": 2,
        "max_attempts": 3,
        "chase_exhausted": false,
        "nobody_signed": false,
        "reminders_enabled": true
      }
    ],
    "total_count": 1
  }
}

Consent timeline for a booking

The ordered per-participant event list — what was sent, whether it was opened, each reminder with its delivery status, what happens next, and the signature (with signed-on-behalf provenance and counter-signatures).

GET /v1/bookings/{id}/consent-timeline

Requires the bookings:read scope. This is also how to read per-participant consent status for a program cohort's enrollments or a session manifest: call it per booking id.

Chase one booking (or one participant)

Runs the same engine as the scheduled chaser: it counts as an attempt, respects the attempt cap, and lands on the timeline like any other send. The 8am–8pm supplier-local send window is NOT applied here — quiet hours govern the automatic chaser only, so this endpoint sends immediately whatever the local clock says.

POST /v1/bookings/{id}/chase-consents

Requires the bookings:write scope.

Body Parameters

Parameter	Type	Description
customer_id	integer (optional)	Chase only this participant's unsigned forms. Omit to chase everyone on the booking who still hasn't signed.

Success (200 OK)

{
  "data": {
    "message": "Reminder sent to everyone on this booking who still hasn't signed.",
    "pairs_chased": 2
  }
}

No reminder sent (422)

{
  "error": {
    "code": "no_reminder_sent",
    "message": "No reminder is due yet. The last one went out recently."
  }
}

Bulk chase

Chase several bookings in one call — the API twin of the tracker's bulk "Send reminders" action. Each booking runs through the same engine; bookings with nothing due simply report their reason.

POST /v1/bookings/chase-consents

Requires the bookings:write scope.

Body Parameters

Parameter	Type	Description
booking_ids	integer[]	1–100 booking ids to chase

Success (200 OK)

{
  "data": {
    "bookings_chased": 2,
    "results": [
      { "booking_id": 123, "sent": true, "reason": null, "pairs_chased": 2 },
      { "booking_id": 124, "sent": false, "reason": "nothing_unsigned", "pairs_chased": 0 },
      { "booking_id": 999, "sent": false, "reason": "not_found" }
    ]
  }
}

Ids that don't belong to your account report not_found — they are never chased and never leak.

A draft booking reports draft and is not chased.

Example Request

curl -X POST "https://app.equipdash.com/api/v1/bookings/chase-consents" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"booking_ids": [123, 124]}'

Errors

Status	Code	Description
401	authentication_required	No API key provided
401	invalid_api_key	Invalid API key
403	insufficient_scope	API key lacks the required 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	Switched off, not live, all signed, limit reached, or a reminder went out in the last 15 minutes