# 30 Minute Session - Perfect for getting started! with Gesa Pickbrenner

> This session is perfect for getting to know each other and your needs and ideas. We will take a look at your idea from top to bottom, and I will suggest possible strategies for bringing it to life. You will gain clarity on how to approach the design process, what's needed, and what you can expect from the collaboration. What we will cover: Basics of your idea Roadmap on how to proceed Answering (almost) all of the questions you have Lots of creative fun! Please send me any files you'd like to work on in advance via design@phialo.de.

- Host: Gesa Pickbrenner
- Duration: 30 min
- Location: Google Meet, Cal Video
- Host time zone: Europe/Berlin
- Confirmation: Bookings are confirmed instantly.
- Payment: required, and collected on the booking page.
- Booking page: https://cal.com/gesapickbrenner/30mingesapickbrenner
- Event type id: 441445

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=441445&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": 441445,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "bookingFieldsResponses": {
    "prior-experience-level": "…",
    "your-idea": "…",
    "Terms": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `prior-experience-level` (Do you have any prior experience in Blender?), `your-idea` (What would you like to improve on, especially at first?), `Terms` (I agree to Skillshare's 1-on-1 Terms — skl.sh/1-on-1-terms — and consent to my email address being shared with the session teacher.)
- Optional fields: none
- `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.
