Get bookable time slots for a booking link

Compute the bookable time slots for a booking link over a date range — exactly what a guest sees on the public booking page, through the same shared engine: live roster resolution, calendar free/busy + working hours, the min-booking-notice floor, and the existing-bookings buffer/overbooking screen against Aura's own calls table.

Semantics:

• start_date/end_date are inclusive UTC calendar days; the range spans at most 31 days and must start today or later.
• The window is additionally clamped to the link's booking horizon (available_days_in_future).
• Slot times are unix seconds (UTC); timezone is echoed back for client-side formatting only.
• An empty roster or a fully-booked range returns slots: [] (200).

Expected failures are typed, never a bare 500:

• 400 — invalid date range
• 422 — the link's configuration was rejected by the availability provider (e.g. a misconfigured grant or calendar)
• 502 — the availability provider is degraded (5xx / timeout)

curl -X GET "https://api.aura-app.ai/v1/booking-links/550e8400-e29b-41d4-a716-446655440000/availability?start_date=2026-07-10&end_date=2026-07-17"

{
  "data": {
    "slots": [
      {
        "emails": [
          "string"
        ],
        "end_time": 1783509300,
        "start_time": 1783507500
      }
    ],
    "timezone": "Europe/Berlin"
  },
  "success": true
}

{
  "code": "NOT_FOUND",
  "error": "Lead not found",
  "requestId": "req_abc123",
  "success": false
}

{
  "code": "NOT_FOUND",
  "error": "Lead not found",
  "requestId": "req_abc123",
  "success": false
}

{
  "code": "NOT_FOUND",
  "error": "Lead not found",
  "requestId": "req_abc123",
  "success": false
}

{
  "code": "NOT_FOUND",
  "error": "Lead not found",
  "requestId": "req_abc123",
  "success": false
}

{
  "code": "NOT_FOUND",
  "error": "Lead not found",
  "requestId": "req_abc123",
  "success": false
}