Get Booking Signing Link
One link that covers a whole booking. Send it to the customer and everyone on the booking signs their own form from it, with their details already filled in. Someone who is not on the booking yet can add themselves, and signing adds them as a participant.
Use this instead of handing out a separate link per person.
The link is reusable and stays valid until the booking's links are revoked (for example when the booking is canceled). Requesting it twice returns the same URL.
Endpointโ
GET /v1/bookings/{id}/waiver-link
Authenticationโ
Requires an API key with the bookings:read scope.
Path Parametersโ
| Parameter | Type | Description |
|---|---|---|
id | integer | Booking ID |
Responseโ
Success (200 OK)โ
{
"data": {
"waiver_signing_url": "https://app.equipdash.com/sign/kA9x...QpZ2"
},
"meta": {
"request_id": "req_abc123",
"timestamp": "2026-09-09T09:00:00+00:00"
}
}
Nothing to sign (422)โ
{
"error": {
"code": "no_waivers_required",
"message": "This booking has nothing to sign."
}
}
Returned when no waiver or form applies to what this booking contains.
Also on the booking payloadโ
The booking detail response carries the same URL as waiver_signing_url, so a single GET /v1/bookings/{id} is enough when you already need the booking. It is null when the booking has nothing to sign, and it is not present on list endpoints.
Example Requestโ
curl "https://app.equipdash.com/api/v1/bookings/123/waiver-link" \
-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:read scope |
| 403 | forbidden | Booking belongs to another supplier |
| 404 | not_found | Booking not found |
| 422 | no_waivers_required | Nothing on this booking needs signing |