# Discovery call with Val

> I’m building dokus and want to understand how people work with documents and business email today. Tell me how it works in your company, what takes more effort than it should, and what you wish you could do differently. It could be something you do manually or something you want to build into your own product. You don’t need to prepare anything or know what the solution should be. One example is enough to start. I can show you what I’m building too, if it’s relevant. You’ll be talking directly with me, the founder and developer.

- Host: Val
- Duration: 30 min
- Location: Google Meet, Cal Video
- Host time zone: Asia/Muscat
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/primorrow/discovery-call
- Event type id: 7156581

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=7156581&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": 7156581,
  "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.
- `location` is optional; without it the booking uses the event’s first location.
