Eventcube is an event ticketing platform with white-labeling capabilities and an API you can use with you existing site and systems.
You can find the API documentation here: https://api-docs.eventcube.io/.
How is the request made to the Eventcube API to create an additional ticket?
Here you can find the API call to create a ticket for a given event.
After you've created an event and a ticket (via the API or the Eventcube Admin) and connected your Stripe account from the Eventcube admin, you can call the Add Ticket to Basket.
This gives you a basket token you can then use to keep adding tickets.
How do payments work with the Eventcube API?
Handle payments on Eventcube
The cart ID is returned in the response of the Add Ticket to Basket API call. You can then use this cart ID to call the Basket detail API endpoint to get the `checkout_url`.
You can then redirect the user to the `checkout_url` to complete the payment for the tickets currently in the customer's basket. This page will be hosted on your Eventcube store. After completing the payment, the user will receive a confirmation email from Eventcube.
Handle payments on your end
To turn a Basket into an Order, you can call this API endpoint to create the Order: https://api-docs.eventcube.io/#6d8d323d-0a09-4bef-a0a0-3b400e36e7d6.
Do this after you've received payment confirmation from the system you're using to process payments.
The customer will then optionally receive an email from Eventcube with the order details.
Levels of integration using the Eventcube API
There are a few options depending how far your want to take the integration:
Option 1: Easiest
The easiest - simply create the events and tickets via the API, then store the returned event URL (e.g., storename.eventcube.io/event) and link out to it from the existing site.
The whole event display, basket, and checkout will be fully hosted on Eventcube, so you don't need to do anything further.
Option 2: Slightly more advanced
Generate the embed code to embed the event on an existing site. You can use Enhanced Embeds for more control here, too.
Once you select your tickets through checkout, the flow is then fully hosted. (e.g., lvl.global, remo.co)
Option 3: Hybrid approach
Use the API to pull back the event details and tickets, and generate the basket on the existing site, then use the returned "Basket Token" to send them through a hosted checkout flow.
Basically, you're developing everything up until checkout and then hand it off to Eventcube.
Option 4: Fully API-driven
You can go for a fully api-driven approach and build things like payment flow on your own side and then use the confirm order endpoint to generate and issue the order. (e.g., lokkaroom).
Check out the PDF below for a visual representation of each option.
Please get in touch with the Eventcube Support Team for more questions.
Related articles: