docs: v2 rolling window and authentication

apps/api/v2/swagger/documentation.json

@@ -6532,7 +6532,7 @@
           "rolling": {
             "type": "boolean",
             "example": true,
-            "description": "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date."
+            "description": "\n      Determines the behavior of the booking window:\n      - If **true**, the window is rolling. This means the number of available days will always equal the specified 'value' \n        and will adjust dynamically as bookings are made. For example, if 'value' is 3 and there is only availability on Mondays, \n        a booker attempting to schedule on November 10 will see slots on November 11, 18, and 25. As one of these days \n        becomes fully booked, a new day (e.g. December 2) will open up to ensure 3 available days are always visible.\n      - If **false**, the window is fixed. This means the booking window only considers the next 'value' days from the\n        moment someone is trying to book. For example, if 'value' is 3, availability is only on Mondays, and the current \n        date is November 10, the booker will only see slots on November 11 because the window is restricted to the next \n        3 calendar days (November 10–12).\n    "
           }
         },
         "required": [
@@ -6560,7 +6560,7 @@
           "rolling": {
             "type": "boolean",
             "example": true,
-            "description": "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date."
+            "description": "\n      Determines the behavior of the booking window:\n      - If **true**, the window is rolling. This means the number of available days will always equal the specified 'value' \n        and adjust dynamically as bookings are made. For example, if 'value' is 3 and availability is only on Mondays, \n        a booker attempting to schedule on November 10 will see slots on November 11, 18, and 25. As one of these days \n        becomes fully booked, a new day (e.g., December 2) will open up to ensure 3 available days are always visible.\n      - If **false**, the window is fixed. This means the booking window only considers the next 'value' days from the\n        moment someone is trying to book. For example, if 'value' is 3, availability is only on Mondays, and the current \n        date is November 10, the booker will only see slots on November 11 because the window is restricted to the next \n        3 calendar days (November 10–12).\n    "
           }
         },
         "required": [

docs/api-reference/v2/introduction.mdx

@@ -5,7 +5,17 @@ description: 'Introduction to Cal.com API v2 endpoints'
 
 ## Authentication
 
-The Cal.com API uses API keys to authenticate requests. You can view and manage your API keys in your settings page under the security tab in Cal.com.
+The Cal.com API has 3 authentication methods:
+
+1. API key
+2. Platform OAuth client credentials
+3. Managed user access token
+
+If you are a platform customer you don't need an API key and must instead use OAuth credentials or a managed user access token. We cover when to use which below.
+
+### 1. API key
+
+You can view and manage your API keys in your settings page under the security tab in Cal.com.
 
 <img src="/images/i1600x899-DllqhV6w_3Vj_oxtjov.png" />
 
@@ -24,3 +34,40 @@ Authentication to the API is performed via the Authorization header. For example
 in your request header.
 
 All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
+
+### 2. OAuth client credentials
+You need to use OAuth credentials when:
+
+1. Managing managed users [API reference](https://cal.com/docs/api-reference/v2/platform-managed-users/create-a-managed-user)
+2. Creating OAuth client webhooks [API reference](https://cal.com/docs/api-reference/v2/platform-webhooks/create-a-webhook)
+3. Refreshing tokens of managed user [API reference](https://cal.com/docs/api-reference/v2/oauth/post-v2oauth-refresh)
+4. Teams related endpoints. Managing organization teams [API reference](https://cal.com/docs/api-reference/v2/orgs-teams/create-a-team), adding managed users as members  to teams [API reference](https://cal.com/docs/api-reference/v2/orgs-teams-memberships/create-a-membership), creating team event types [API reference](https://cal.com/docs/api-reference/v2/orgs-event-types/create-an-event-type).
+
+OAuth credentials can be accessed in the platform dashboard https://app.cal.com/settings/platform after you have created an OAuth client. Each one has an ID and secret. You then need to pass them as request headers:
+
+1. `x-cal-client-id` - ID of the OAuth client.
+2. `x-cal-secret-key` - secret of the OAuth client.
+
+### 3. Managed user access token
+
+After you create a managed user you will receive its access and refresh tokens. The response also includes managed user's id, so we recommend you to add new properties to your users table calAccessToken, calRefreshToken and calManagedUserId to store this information.
+
+You need to use access token when managing managed user's:
+1. Schedules [API reference](https://cal.com/docs/api-reference/v2/schedules/create-a-schedule)
+2. Event types [API reference](https://cal.com/docs/api-reference/v2/event-types/create-an-event-type)
+3. Bookings - some endpoints like creating a booking is public, but some like getting all managed user's bookings require managed user's access token [API reference](https://cal.com/docs/api-reference/v2/bookings/get-all-bookings)
+
+It is passed as an authorization bearer request header Authorization: Bearer <access-token>.
+
+Validity period: access tokens are valid for 60 minutes and refresh tokens for 1 year, and tokens can be refreshed using the refresh endpoint [API reference](https://cal.com/docs/api-reference/v2/oauth/post-v2oauth-refresh). After refreshing you will receive the new access and refresh tokens that you have to store in your database.
+
+Recovering tokens: if you ever lose managed user's access or refresh tokens, you can force refresh them using the OAuth client credentials and store them in your database [API reference](https://cal.com/docs/api-reference/v2/platform-managed-users/force-refresh-tokens).
+
+## Navigating endpoints
+Platform customers have the following endpoints available:
+
+1. Endpoints prefixed with "Platform".
+2. Endpoints with no prefix e.g "Bookings", "Event Types".
+3. If you are at least on the ESSENTIALS plan, then all endpoints prefixed with "Orgs" except "Orgs / Attributes".
+
+Non-platform customers have all the endpoints except the ones prefixed with "Platform".

docs/api-reference/v2/openapi.json

@@ -6064,7 +6064,7 @@
           "rolling": {
             "type": "boolean",
             "example": true,
-            "description": "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date."
+            "description": "\n      Determines the behavior of the booking window:\n      - If **true**, the window is rolling. This means the number of available days will always equal the specified 'value' \n        and adjust dynamically as bookings are made. For example, if 'value' is 3 and availability is only on Mondays, \n        a booker attempting to schedule on November 10 will see slots on November 11, 18, and 25. As one of these days \n        becomes fully booked, a new day (e.g., December 2) will open up to ensure 3 available days are always visible.\n      - If **false**, the window is fixed. This means the booking window only considers the next 'value' days from the\n        moment someone is trying to book. For example, if 'value' is 3, availability is only on Mondays, and the current \n        date is November 10, the booker will only see slots on November 11 because the window is restricted to the next \n        3 calendar days (November 10–12).\n    "
           }
         },
         "required": ["type", "value"]
@@ -6085,7 +6085,7 @@
           "rolling": {
             "type": "boolean",
             "example": true,
-            "description": "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date."
+            "description": "\n      Determines the behavior of the booking window:\n      - If **true**, the window is rolling. This means the number of available days will always equal the specified 'value' \n        and adjust dynamically as bookings are made. For example, if 'value' is 3 and availability is only on Mondays, \n        a booker attempting to schedule on November 10 will see slots on November 11, 18, and 25. As one of these days \n        becomes fully booked, a new day (e.g., December 2) will open up to ensure 3 available days are always visible.\n      - If **false**, the window is fixed. This means the booking window only considers the next 'value' days from the\n        moment someone is trying to book. For example, if 'value' is 3, availability is only on Mondays, and the current \n        date is November 10, the booker will only see slots on November 11 because the window is restricted to the next \n        3 calendar days (November 10–12).\n    "
           }
         },
         "required": ["type", "value"]
@@ -11792,6 +11792,10 @@
             "type": "boolean",
             "example": true
           },
+          "createdAt": {
+            "type": "string",
+            "example": "2024-08-13T15:30:00Z"
+          },
           "metadata": {
             "type": "object",
             "example": {
@@ -11832,6 +11836,7 @@
           "eventTypeId",
           "eventType",
           "absentHost",
+          "createdAt",
           "attendees"
         ]
       },
@@ -11912,6 +11917,10 @@
             "type": "boolean",
             "example": true
           },
+          "createdAt": {
+            "type": "string",
+            "example": "2024-08-13T15:30:00Z"
+          },
           "metadata": {
             "type": "object",
             "example": {
@@ -11956,6 +11965,7 @@
           "eventTypeId",
           "eventType",
           "absentHost",
+          "createdAt",
           "attendees",
           "recurringBookingUid"
         ]

packages/platform/types/event-types/event-types_2024_06_14/inputs/booking-window.input.ts

@@ -38,6 +38,18 @@ class BookingWindowBase {
   type!: BookingWindowPeriodInputType_2024_06_14;
 }
 
+const rollingDescription = `
+      Determines the behavior of the booking window:
+      - If **true**, the window is rolling. This means the number of available days will always equal the specified 'value' 
+        and adjust dynamically as bookings are made. For example, if 'value' is 3 and availability is only on Mondays, 
+        a booker attempting to schedule on November 10 will see slots on November 11, 18, and 25. As one of these days 
+        becomes fully booked, a new day (e.g., December 2) will open up to ensure 3 available days are always visible.
+      - If **false**, the window is fixed. This means the booking window only considers the next 'value' days from the
+        moment someone is trying to book. For example, if 'value' is 3, availability is only on Mondays, and the current 
+        date is November 10, the booker will only see slots on November 11 because the window is restricted to the next 
+        3 calendar days (November 10–12).
+    `;
+
 // Separate classes for different value types
 export class BusinessDaysWindow_2024_06_14 extends BookingWindowBase {
   @IsNumber()
@@ -49,8 +61,7 @@ export class BusinessDaysWindow_2024_06_14 extends BookingWindowBase {
   @IsBoolean()
   @ApiPropertyOptional({
     example: true,
-    description:
-      "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date.",
+    description: rollingDescription,
   })
   rolling?: boolean;
 
@@ -69,8 +80,7 @@ export class CalendarDaysWindow_2024_06_14 extends BookingWindowBase {
   @IsBoolean()
   @ApiPropertyOptional({
     example: true,
-    description:
-      "If true, the window will be rolling aka from the moment that someone is trying to book this event. Otherwise it will be specified amount of days from the current date.",
+    description: rollingDescription,
   })
   rolling?: boolean;