Custom-confirmation bookings shouldn't need salt to confirm

Question and Answers
1

I am using Nylas only through the API’s.
When I set a configuration as custom-confirmation, a booking is made on a pending state in both calendars.
When I try to use the confirm booking endpoint, a parameter in the body called Salt is mandatory and the only way to obtain it is from the url in the booking email the organiser receives.. but this is not organiser-confirmation.
Is there a way around this or any other way to get the salt parameter? or should it just not be mandatory for custom-conformation bookings?

Thanks for the help,

Alfonso

2

Hi @Alfonso thanks for reaching out and I see this inquiry is on our radar. Let me circle back once I have updates.

3

Is there any updates on this inquiry?

I think it should be possible to confirm a booking via the API-key alone. And maybe also the configuration id.

4

Hello

“custom-confirmation” is not supported yet.

I believe the workaround, for you, would be to use “organizer-confirmation” and decode the booking reference in order to return the salt.

Many thanks,
Samuel R.
Support Engineer, Nylas