fix: fetching event-types of org users apiv2 (#18004)

This commit is contained in:
Morgan
2024-12-05 06:02:19 +00:00
committed by GitHub
parent ab2ab31eef
commit 16a7cf6d04
7 changed files with 255 additions and 36 deletions
+42 -6
View File
@@ -3849,6 +3849,15 @@
"type": "string"
}
},
{
"name": "eventTypeId",
"required": false,
"in": "query",
"description": "Id of the event-type, if this is provided no other parameter is required",
"schema": {
"type": "number"
}
},
{
"name": "usernames",
"required": false,
@@ -3857,6 +3866,33 @@
"schema": {
"type": "string"
}
},
{
"name": "userId",
"required": false,
"in": "query",
"description": "ID of the user you want the get the event-types of, username is not needed when using this parameter",
"schema": {
"type": "number"
}
},
{
"name": "orgSlug",
"required": false,
"in": "query",
"description": "slug of the user's organization if he is in one, orgId is not required if using this parameter",
"schema": {
"type": "string"
}
},
{
"name": "orgId",
"required": false,
"in": "query",
"description": "ID of the organization of the user you want the get the event-types of, orgSlug is not needed when using this parameter",
"schema": {
"type": "number"
}
}
],
"responses": {
@@ -6067,7 +6103,7 @@
"rolling": {
"type": "boolean",
"example": true,
"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 1012).\n "
"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 be 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 1012).\n "
}
},
"required": ["type", "value"]
@@ -6088,7 +6124,7 @@
"rolling": {
"type": "boolean",
"example": true,
"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 1012).\n "
"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 be 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 1012).\n "
}
},
"required": ["type", "value"]
@@ -12100,7 +12136,7 @@
"hosts": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Host"
"$ref": "#/components/schemas/BookingHost"
}
},
"status": {
@@ -12216,7 +12252,7 @@
"hosts": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Host"
"$ref": "#/components/schemas/BookingHost"
}
},
"status": {
@@ -12371,7 +12407,7 @@
"hosts": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Host"
"$ref": "#/components/schemas/BookingHost"
}
},
"status": {
@@ -12482,7 +12518,7 @@
"hosts": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Host"
"$ref": "#/components/schemas/BookingHost"
}
},
"status": {