# RedAssay with Himanshu

> I'll demo RedAssay against a live target: it drives a real browser through the app like a user, captures every backend call it provokes, and replays each candidate before reporting it. You'll see a finding go through the proof gate, and one get held back because the replay couldn't reproduce it. Then I'll walk any number on the public benchmark sheet, including the coverage we don't have yet. Bring a target and your rules of engagement if you want to scope a pilot.

- Host: Himanshu
- Duration: 30 min
- Location: Google Meet
- Host time zone: Asia/Calcutta
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/himanshuat/redassay
- Event type id: 7042382

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=7042382&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": 7042382,
  "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.