# See what your managers are missing with Ruth-Ellen Danquah

> I'm working with a small group of People Leaders on a specific problem: managers make decisions that create tribunal risk or employee relations issues — and by the time the People team finds out, the moment to intervene has passed. ANCHOR captures the decision at the point it's made. This session is not a demo. I want your read on whether we've identified the right problem, and your input will directly shape how the platform develops. 20 minutes. No pitch. No follow-up pressure.

- Host: Ruth-Ellen Danquah
- Duration: 20 min
- Location: Cal Video
- Host time zone: Europe/London
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/ruth-ellen-danquah-orl6s0/founding-input-session
- Event type id: 5028378

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5028378&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 5028378,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address)
- Optional fields: `notes` (Additional notes), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
