# New bug in Wix Bookings API

**URL:** <https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750>\
**Category:** Ask the community\
**Tags:** wix-bookings, question, code\
**Created:** [August 26, 2022, 10:55am UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750 "2022-08-26T10:55:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![info80774](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/info80774/32/22831_2.png) [@info80774](https://forum.wixstudio.com/u/info80774)\
**Post date:** [August 26, 2022, 10:55am UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750/1 "2022-08-26T10:55:57Z")

</div>

This seems to have been introduced in the past couple of days as we noticed the behaviour change on Wednesday 24th despite the code being stable and working fine for 2 months.

Calling wixBookings . checkoutBooking ( bookingInfo ) with custom formFields no longer shows those form field details on the Calendar booking.

Any default form field (those with IDs  
00000000-0000-0000-0000-000000000001  
00000000-0000-0000-0000-000000000002  
00000000-0000-0000-0000-000000000003  
)  
Seem to work fine. However passing through valid custom field id/value pairs are getting ignored by checkoutBooking even though the booking returns as successful with a valid booking ID.

While I’ve raised this as a bug with support, I hope this catches the attention of any Wix Velo staff for a speedy resolution as this bug is in production and affecting client sites.

Thanks.

---

<div class="post-metadata">

**Author:** ![jacobg](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/jacobg/32/29611_2.png) [@jacobg](https://forum.wixstudio.com/u/jacobg)\
**Post date:** [August 26, 2022, 11:03am UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750/2 "2022-08-26T11:03:44Z")

</div>

Hi, thanks you raising this issue.  
I’m from Wix Bookings, I will investigate this and update once this is resolved.

---

<div class="post-metadata">

**Author:** ![info80774](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/info80774/32/22831_2.png) [@info80774](https://forum.wixstudio.com/u/info80774)\
**Post date:** [August 26, 2022, 2:40pm UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750/3 "2022-08-26T14:40:37Z")

</div>

Jacob, thanks so much for taking a look… please do get in touch if you need further details like examples, booking IDs etc. as it’s hard to share some of this further info on public forum.

---

<div class="post-metadata">

**Author:** ![jacobg](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/jacobg/32/29611_2.png) [@jacobg](https://forum.wixstudio.com/u/jacobg)\
**Post date:** [August 28, 2022, 12:24pm UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750/4 "2022-08-28T12:24:41Z")

</div>

Hi, please retry now.

---

<div class="post-metadata">

**Author:** ![info80774](https://sea1.discourse-cdn.com/wix/user_avatar/forum.wixstudio.com/info80774/32/22831_2.png) [@info80774](https://forum.wixstudio.com/u/info80774)\
**Post date:** [August 29, 2022, 11:20am UTC](https://forum.wixstudio.com/t/new-bug-in-wix-bookings-api/36750/5 "2022-08-29T11:20:13Z")

</div>

Jacob, you’re a star! Thanks for looking at this and the quick turnaround.

Wix Bookings is an excellent app and API, great to see it well supported.