# Hosted Scheduling Booking Error

**URL:** <https://forums.nylas.com/t/hosted-scheduling-booking-error/448>\
**Category:** Question and Answers\
**Tags:** scheduler\
**Created:** [September 16, 2024, 5:49pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448 "2024-09-16T17:49:25Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 16, 2024, 5:49pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/1 "2024-09-16T17:49:25Z")

</div>

When using the hosted scheduler in this form: [Hosted Scheduling Pages | Nylas Docs](https://developer.nylas.com/docs/v3/scheduler/hosted-scheduling-pages/#create-a-hosted-scheduling-page)

I am getting this error when trying to submit the booking when I pass in query params:

Create Booking Error  
json: cannot unmarshal object into Go struct field CreateBookingRequest.additional\_fields of type string

@Blag

---

<div class="post-metadata">

**Author:** ![Blag](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.nylas.com/blag/32/9_2.png) [@Blag](https://forums.nylas.com/u/Blag)\
**Post date:** [September 16, 2024, 7:52pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/2 "2024-09-16T19:52:46Z")

</div>

Hello @sboynton Already requested some help on this one 🙂

---

<div class="post-metadata">

**Author:** ![antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@antoine](https://forums.nylas.com/u/antoine)\
**Post date:** [September 16, 2024, 7:58pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/3 "2024-09-16T19:58:39Z")

</div>

Hey @sboynton would you mind showing me what you mean by query params? Or add any screenshots you think might be relevant?  
Thank you!

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 16, 2024, 8:14pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/4 "2024-09-16T20:14:30Z")

</div>

@antoine with the hosted configuration, I go to this link:

`https://book.nylas.com/us/<client_id>/dummy_slug?name=sam&email=samsemail&phone_number=123`

 ![image](https://us1.discourse-cdn.com/flex015/uploads/nylas3/original/1X/1b86d1968839272c05fdfbb125b1f581ab81d3a4.png)

You can see that we navigate from our page to this page, and hope to pre-populate some fields based on information coming from our app… The boxes are properly filled in for us, but when we go to click ‘book now’ we get this error.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/nylas3/original/1X/520d154e2371eddbf88ff5bd5e79355fd3aecaca.png)

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 16, 2024, 8:15pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/5 "2024-09-16T20:15:27Z")

</div>

In the above example, please assume my email is proper. That was just a poor example for that field, same goes for the phone number. Thanks

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 16, 2024, 8:26pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/6 "2024-09-16T20:26:34Z")

</div>

@antoine another question we had during this implementation flow was… Is there a way to store some of our unique data on event bookings? We’ve seen references to `additional_fields` and `metadata` but have been unsuccessful in using them. In this flow for instance, if we wanted `feed_id` to be stored on the event, would it? In other words, where do the results of these custom fields get saved to? We’ve run some tests and are not seeing these values be populated onto nylas events. Thanks for the help 👍

---

<div class="post-metadata">

**Author:** ![antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@antoine](https://forums.nylas.com/u/antoine)\
**Post date:** [September 16, 2024, 8:46pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/7 "2024-09-16T20:46:53Z")

</div>

@sboynton thanks for raising this - I think what you’ve discovered is a legitimate bug. I looped in our engineers and they’ll be fixing it today, and releasing it in the coming days. Once the fix is released, I’ll be sure to comment here!

Regarding metadata, all additional fields are stored in the /booking objects - we are working to add that information to the GET /bookings response as it’s not returned currently. However, our webhooks _do_ currently return that information (if you subscribe to booking.created webhooks). [Notification schemas | Nylas Docs](https://developer.nylas.com/docs/v3/notifications/notification-schemas/#scheduler-notifications)

---

<div class="post-metadata">

**Author:** ![antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@antoine](https://forums.nylas.com/u/antoine)\
**Post date:** [September 16, 2024, 8:47pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/8 "2024-09-16T20:47:39Z")

</div>

I should mention that additional fields are currently displayed in the confirmation emails we send to guests and hosts!

---

<div class="post-metadata">

**Author:** ![dhruv](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dhruv](https://forums.nylas.com/u/dhruv)\
**Post date:** [September 17, 2024, 4:15am UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/9 "2024-09-17T04:15:16Z")

</div>

@sboynton just upgrade the version of web-elements or nylas-react whatever you are using it will fix the issue

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 17, 2024, 2:06pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/10 "2024-09-17T14:06:37Z")

</div>

I’m on the latest version, and on acceptable node version. It also shouldnt have any effect since we are using their hosted version

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 19, 2024, 2:13pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/11 "2024-09-19T14:13:58Z")

</div>

@antoine any update on this bug fix? It is currently halting our workflow.

---

<div class="post-metadata">

**Author:** ![antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@antoine](https://forums.nylas.com/u/antoine)\
**Post date:** [September 20, 2024, 4:42pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/12 "2024-09-20T16:42:44Z")

</div>

@sboynton the fix should be released today!

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 23, 2024, 3:20pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/13 "2024-09-23T15:20:26Z")

</div>

@antoine Thanks, I can confirm this works and helps a lot. Just another question… is there a way to force the additional fields to be read only or hidden. In v2 we were able to but it seems like v3 might have changed to disallow this. In this example we would pre-populate the fields below email and keep them hidden or read-only

 ![image](https://us1.discourse-cdn.com/flex015/uploads/nylas3/original/1X/faf3262e7ec2deef6dcf24a496b000c9ed048d3e.png)

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 24, 2024, 5:03pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/14 "2024-09-24T17:03:48Z")

</div>

> **[Scheduler v2 booking flow query parameters | Nylas Docs](https://developer.nylas.com/docs/v2/scheduler/scheduler-book-query-params/#booking-flow-query-parameters-examples)**
>
> When you send users to a booking page, you can pass in your query parameters using the page URL and pre-populate input fields.

This is what we want for v3. Any help?

---

<div class="post-metadata">

**Author:** ![sboynton](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@sboynton](https://forums.nylas.com/u/sboynton)\
**Post date:** [September 25, 2024, 2:05pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/15 "2024-09-25T14:05:30Z")

</div>

@blag Would you mind taking a look at my question above? Thanks a lot

---

<div class="post-metadata">

**Author:** ![Blag](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.nylas.com/blag/32/9_2.png) [@Blag](https://forums.nylas.com/u/Blag)\
**Post date:** [September 25, 2024, 2:29pm UTC](https://forums.nylas.com/t/hosted-scheduling-booking-error/448/16 "2024-09-25T14:29:41Z")

</div>

Sure thing @sboynton Let me nudge the right people 😉
