[#870] Booking confirmation email trigger logic

Migrated from Redmine #870 | Author: Jet Lu
Status: Closed | Priority: High, I’m very impatient | Created: 2022-04-19


Hi, I am not sure what setting I have done which makes this single ‘book’ API below triggers the confirmation email instead of after calling the ‘approve’ API. Please see the API and payload below.

I’d like to know the logic of confirmation email triggering or some settings in regards to it so I can revert back. Thanks.

Book API, POST: “https://user-api.simplybook.me
Payload:
{
jsonrpc: “2.0”,
method: “book”,
params: [
“10”,
5,
“2022-04-21”,
“09:00:00”,
{
name: “Guest”,
email: “abc@test.com”,
},
{
terms: true,
handle_invoice: true,
},
1,
],
id: 2,
}

Approve API, PUT: https://user-api-v2.simplybook.me/admin/bookings/123/approve

Dmytro Bondarev wrote:

Hi,

Please provide company login or public site url.

Jet Lu wrote:

Hi, this is the URL - http://chadstone.secure.bookings.vicinity.com.au/ , and the event is Luminous.

Thanks.

Dmytro Bondarev wrote:

The “Approve booking” custom feature is disabled for you. You need to enable it first to use approve booking.

Jet Lu wrote:

Thanks for your reply, that’s exactly the case.

I have discussed this with the team, and the reason they turn the ‘approve’ feature off is: for each paid booking, they have to go to the simplybooking and manually approve it. However, it is all automatic on the staging simplybooking: https://chadstoneqa.secure.simplybook.me. The difference between the two experiences is the production one is using real credit cards while the staging is using a dummy card. The setting difference is the staging is using the Stripe test key while the production is using the live key.

Would you please troubleshoot the settings for us? We’d really like to avoid manually approving for every single customer as they could be thousand for one event. Thanks!