Api bookingWindow and successRedirectUrl NOT working

[Tradetechnique]

Hi,
I want to create event with event-types .
The event is created but successRedirectUrl and bookingWindow are ignored with no error message.
I sent :
{
"eventData": {
"title": "Consultation One-to-Oneb",
"description": "Une session de consultation individuelle b",
"length": 60,
"slug": "consultation-one-to-oneb",
"hidden": false,
"slotInterval": 15,
"locations": [{"type": "address","address": "123 Example St, City, Country","public": true}],
"disableGuests": true,
"successRedirectUrl": "https://www.cosmocareportal.com",
"scheduleId": "abc123",
"bookingWindow": {"type": "range","value": ["2025-02-15","2025-02-15"],"rolling": false}
}
}

Thanks

[dosubot[bot]]

Hey @Tradetechnique! 👋 I'm here to help you out with any bugs, questions, or contributions. I'm a bot designed to assist you while you wait for a human maintainer.

The issue you're experiencing with successRedirectUrl and bookingWindow being ignored might be due to incorrect data types or formats. Here are some things to check:

1. successRedirectUrl: Ensure that the URL is a valid string. It should be in a proper URL format, and it is nullable, meaning it can be set to null if not needed ^[1].

2. bookingWindow: This field should be an array, and the items in the array should follow one of the specified schemas: BusinessDaysWindow_2024_06_14, CalendarDaysWindow_2024_06_14, or RangeWindow_2024_06_14 ^[1]. In your case, the bookingWindow is set as an object with a type of "range", which might not match the expected schema. Ensure that the format aligns with the expected schema.

You might want to verify the structure of the bookingWindow to ensure it matches one of the accepted schemas. If the issue persists, consider checking the API documentation or examples for the correct usage of these fields.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[Tradetechnique]

Hello,

I am using the create event type API (https://api.cal.com/v2/event-types). When I send a request, the event is successfully created on Cal.com, but certain parameters—specifically bookingWindow, successRedirectUrl, and scheduleId—are being ignored.

Could you clarify why these parameters are not being applied?

Additionally, I would like to add bookingFields to the event. Could you provide guidance on how to do this?

Below is an example of my API request along with the response.

Request:
JSON

{

"eventData": {

"title": "Consultation One-to-Oneb",

"description": "Une session de consultation individuelle b",

"length": 60,

"slug": "consultation-one-to-oneb",

"hidden": false,

"slotInterval": 15,

"locations": [{"type": "address","address": "123 Example St, City, Country","public": true}],

"disableGuests": true,

"successRedirectUrl": "https://www.cosmocareportal.com",

"scheduleId": "abc123",

"bookingWindow": {"type": "range","value": ["2025-02-15","2025-02-15"]}

}

}

Response:
JSON

{

"status": "success",

"data": {

    "id": 1775126,

    "title": "Consultation One-to-Oneb",

    "slug": "consultation-one-to-oneb",

    "description": "Une session de consultation individuelle b",

    "position": 0,

    "locations": [

        {

            "type": "address",

            "address": "123 Example St, City, Country"

        }

    ],

    "length": 60,

    "offsetStart": 0,

    "hidden": false,

    "userId": 1287521,

    "profileId": null,

    "teamId": null,

    "useEventLevelSelectedCalendars": false,

    "eventName": null,

    "parentId": null,

    "bookingFields": null,

    "timeZone": null,

    "periodType": "UNLIMITED",

    "periodStartDate": null,

    "periodEndDate": null,

    "periodDays": null,

    "periodCountCalendarDays": null,

    "lockTimeZoneToggleOnBookingPage": false,

    "requiresConfirmation": false,

    "requiresConfirmationWillBlockSlot": false,

    "requiresConfirmationForFreeEmail": false,

    "requiresBookerEmailVerification": false,

    "autoTranslateDescriptionEnabled": false,

    "recurringEvent": null,

    "disableGuests": true,

    "hideCalendarNotes": false,

    "hideCalendarEventDetails": false,

    "minimumBookingNotice": 120,

    "beforeEventBuffer": 0,

    "afterEventBuffer": 0,

    "seatsPerTimeSlot": null,

    "onlyShowFirstAvailableSlot": false,

    "seatsShowAttendees": false,

    "seatsShowAvailabilityCount": true,

    "schedulingType": null,

    "scheduleId": null,

    "price": 0,

    "currency": "usd",

    "slotInterval": 15,

    "metadata": null,

    "successRedirectUrl": null,

    "forwardParamsSuccessRedirect": true,

    "bookingLimits": null,

    "durationLimits": null,

    "isInstantEvent": false,

    "instantMeetingExpiryTimeOffsetInSeconds": 90,

    "instantMeetingScheduleId": null,

    "instantMeetingParameters": [],

    "assignAllTeamMembers": false,

    "assignRRMembersUsingSegment": false,

    "rrSegmentQueryValue": null,

    "useEventTypeDestinationCalendarEmail": false,

    "isRRWeightsEnabled": false,

    "maxLeadThreshold": null,

    "allowReschedulingPastBookings": false,

    "eventTypeColor": null,

    "rescheduleWithSameRoundRobinHost": false,

    "secondaryEmailId": null

}

}

[dosubot[bot]]

The parameters bookingWindow, successRedirectUrl, and scheduleId are not being applied correctly in your API request for the following reasons:

1. bookingWindow: This parameter is not included in the schemaEventTypeCreateParams or schemaEventTypeBaseBodyParams, which means it is not recognized by the API when creating an event type. To use bookingWindow, it needs to be added to the schema definitions in the API code ^[1].

2. successRedirectUrl and scheduleId: These parameters are present in the schemas, so they should be applied correctly if provided in the request. Ensure that the values you are passing are in the correct format and that there are no additional constraints or conditions in the API that might be affecting their application ^[1].

To add bookingFields to the event, you can include them in the request body when creating the event type. The bookingFields parameter is defined as optional in both schemaEventTypeCreateParams and schemaEventTypeEditParams. Make sure the bookingFields you provide match the expected structure defined by eventTypeBookingFields ^[1]. Here is an example of how you might structure bookingFields:

"bookingFields": [
  {
    "isDefault": false,
    "type": "text",
    "slug": "favorite-movie",
    "label": "Favorite Movie",
    "required": true,
    "placeholder": "Enter your favorite movie",
    "disableOnPrefill": false,
    "hidden": false
  }
]

Ensure that the bookingFields structure aligns with the expected format for the API to process them correctly ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[Tradetechnique]

I'm using api V2.
bookingWindow exist for create event.