# Scoping Call with Adrian Rusan

> 30 minutes to find out which offer fits your work, if any. Bring one real piece of it: a backlog slice, a repo, a process you'd want automated. You leave with a fixed scope and a fixed price, or a straight "not a fit". No obligation. Every PR I deliver is security-reviewed line by line by a senior engineer before it reaches you.

- Host: Adrian Rusan
- Duration: 30 min
- Location: Google Meet
- Host time zone: Europe/Bucharest
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/adrian-rusan/scoping-call
- Event type id: 5489317

## Check availability

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

- Required fields: `name` (Your name), `email` (Email address), `topic` (What's the backlog or project you'd want shipped?)
- Optional fields: `stack` (Your stack?), `timeline` (Rough timeline?), `company` (Company + your role?), `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.
