# Confusing or incomplete API Documentation

**URL:** <https://forums.nylas.com/t/confusing-or-incomplete-api-documentation/757>\
**Category:** Question and Answers\
**Created:** [July 3, 2025, 9:18pm UTC](https://forums.nylas.com/t/confusing-or-incomplete-api-documentation/757 "2025-07-03T21:18:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kayvannj](https://avatars.discourse-cdn.com/v4/letter/k/dc4da7/32.png) [@kayvannj](https://forums.nylas.com/u/kayvannj)\
**Post date:** [July 3, 2025, 9:18pm UTC](https://forums.nylas.com/t/confusing-or-incomplete-api-documentation/757/1 "2025-07-03T21:18:25Z")

</div>

When using the nylas Confirm Booking Api as documented [here](https://developer.nylas.com/docs/api/v3/scheduler/#tag/bookings/PUT/v3/scheduling/bookings/%7Bbooking_id%7D)  
the Salt in the request body is described as follows:

> The salt extracted from the booking reference embedded in the organizer confirmation link, encoded as a URL-safe base64 string (without padding).

how ever there is no explanation on how to extract the salt from the booking reference! we have experimented with multiple different approaches and have searched the documentaion throughly with no luck!

@ram there is also a similar question here that is unanswered.

> [@Custom-confirmation bookings shouldn't need salt to confirm](https://forums.nylas.com/t/custom-confirmation-bookings-shouldnt-need-salt-to-confirm/707/2):
>
> Hi @Alfonso thanks for reaching out and I see this inquiry is on our radar. Let me circle back once I have updates.

Please advise as where and how we can get the Salt needed for this API.

---

<div class="post-metadata">

**Author:** ![ram](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.nylas.com/ram/32/3_2.png) [@ram](https://forums.nylas.com/u/ram)\
**Post date:** [July 10, 2025, 3:28pm UTC](https://forums.nylas.com/t/confusing-or-incomplete-api-documentation/757/2 "2025-07-10T15:28:36Z")

</div>

@kayvannj thanks for the message, will take a look and circle back.

The previous message [Custom-confirmation bookings shouldn't need salt to confirm - #2 by ram](https://forums.nylas.com/t/custom-confirmation-bookings-shouldnt-need-salt-to-confirm/707/2) was responded to separately, should have shared it on the post, so will look up the response.

---

<div class="post-metadata">

**Author:** ![ram](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.nylas.com/ram/32/3_2.png) [@ram](https://forums.nylas.com/u/ram)\
**Post date:** [July 10, 2025, 3:34pm UTC](https://forums.nylas.com/t/confusing-or-incomplete-api-documentation/757/3 "2025-07-10T15:34:24Z")

</div>

@kayvannj have a look at [decode the booking reference](https://developer.nylas.com/docs/v3/scheduler/retrieve-booking-ids/#decode-booking-reference) that shares a code sample to retrieve the salt.
