# Onboarding with Unosend

> Onboarding call to review your setup, volumes, and requirements and make sure Unosend is configured correctly for your use case. Your current email infrastructure and workflows, Compliance, deliverability, and security needs, Expected volumes, and SLAs. By the end of the call, you’ll have a clear overview of your Unosend setup, recommended best practices, and next steps to get fully live in production.

- Host: Unosend
- Duration: 30 min
- Location: Cal Video
- Host time zone: Asia/Kolkata
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/unosend/onboarding
- Event type id: 5711721

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5711721&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": 5711721,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "title": "…",
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `title` (What is this meeting about?)
- 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.