# CRM Consultation with Ninsei Labs

> Your CRM should fit how you actually sell, not the other way around. We walk through your pipeline, the data you need to see, and what your current setup costs you in daily friction. I'm building my own CRM as a reference case, so this is hands-on, not theory.

- Host: Ninsei Labs
- Duration: 30 min
- Location: Google Meet
- Host time zone: America/Chicago
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/ninseilabs/crm-consultation
- Event type id: 6116379

## Check availability

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