Support

July 21, 2015 at 8:20 am

We want to use your software to be able to sell-out a session when the ticket capacity is reached, however, we need the payment to be submitted on another site through their vendor. (They want to handle the payment process.)

We were thinking of using the API so that it could send the information back to EE to modify the ticket count once the checkout is complete and only gather minor details through EE.

Currently, we are test-driving EE4 and the only information I see about API for it I found in this post (https://eventespresso.com/2015/04/event-espresso-4-rest-api-development-github/). There already appears to be one for EE3, but we like the interface for EE4.

Do you think we need to use EE3 so that we can benefit from the API add-on that already exists?

Today our process is very manual. We have a maximum capacity of 14 seats. Once we sell all 14 seats, a person gets manually emailed to update the website. Depending on the amount of task they are already doing, it can be a delay in updating the site that a session is sold out. While this happens, another person could purchase a seat.

Another reason is that their cart is very basic and lists SKUs that are vague. In the notes/comments field, they are supposed to enter which session/event they want to attend. Sometimes they don’t do this and it requires a manual email follow-up to confirm their selection.

In the end, we are looking to automate 2 things; knowing which session they sign up for and the sessions updating with the status of Sold Out, all of which would start on our site and complete on a vendor’s site.

We also use a manual wait-list too, so EE3 might be the way to go since this feature exists in EE3 only.

Thanks for any help you can provide and if you would rather discuss via phone, please let me know.

Daniel