We are happy to announce that development of the Event Espresso 4 REST API has begun. You are invited to get involved with the API development by: sharing feedback on the direction of the API, contributing code, testing what is already completed, and encouraging others to get involved.
WordPress and Event Espresso Developers will be most interested in the EE4 REST API, because it will allow for faster development of a wide array of features, including custom reporting tools, mobile application development, and theme development. The EE4 REST API will provide an easy to use API, available via HTTP, to grab your site’s event and registration data in simple JSON format. Retrieving or updating data is as simple as sending a HTTP request.
Purpose of the Event Espresso 4 REST API
Other WordPress plugins that intend to use Event Espresso 4 data server-side (in the PHP code) generally do not need to use the API, and can instead use Event Espresso 4’s models, config, and other modules directly. Check out developer.eventespresso.com for tutorials on how to use many of these systems.
Example applications could include:
- Mobile applications for signing attendees into events in Event Espresso
- WordPress plugin that controls Event Espresso data entirely on the client-side
Generally, the work will be organized into 3 main milestones:
- READ functionality (API clients will be able to read just about anything from EE4, including information from add-ons)
- WRITE functionality (API clients will be able to create and update most EE4 info, but we’d like to prevent API clients from breaking the DB so that will be a bit of a challenge)
- Single page checkout (SPCO) functionality (we will want to present similar functionality to SPCO, except over the API. This will require rather tight integration with SPCO in order to keep them almost identical)
Current progress (as of this writing):
- READ functionality is approximately 85% completed. We are actively working on the compatibility with the permissions and capability controls that are built into Event Espresso core.
- WRITE functionality: 0% completed
- SPCO functionality: 0% completed
Generally, the central hub for the API should be the EE4 REST API Github repository and milestones; along with blogging about it from developer.eventespresso.com.
Information for Non-developers
I’m not a developer, how does this affect me?
Not a developer, that’s okay! The Event Espresso REST API will allow other applications (other websites, mobile apps, etc) to access your Event Espresso data through an application programming interface (API).
We recommend you share this with your development team, agency or app developers because they will be excited about this. You should ask them to consider building an integration for the Event Espresso 4 API so that you can use your data in their applications.
Another benefit of the API is that if you want a certain edge case feature that is not available in our core products, you can hire a developer to build it for you, without having to understand the Event Espresso 4 code base.
Have ideas for the API, fill out the survey below or leave a comment.
Information for Developers
How do I get access to the files?
Anyone with an account on Github.com can download and install the EE4 REST API on their site.
How do I get involved?
For the most part, at the time of this writing, we are still in the planing and development stages. Developers that are interested in the Event Espresso 4 REST API can get involved in the development and planning process from within the EE4 REST API page on Github.com.
Participate in a short survey!
How will you, or your company use the EE4 REST API? Let us know by filling out the survey below.
Has this been prioritized over features that were standard to EE3 such as promo codes which has seemingly been shelved indefinitely? What about the stability of Event Espresso with large events that have multiple ticket options? There is clearly a major bug/issue with this that has not been addressed by your team
Nope, this has not been prioritized over other features. It is actually being developed at the same time as other features. We have more than one developer, each with skills and specialties working on multiple different projects.
The Promotions and Multiple Event Registration add-ons have been held up because we discovered that the EE4 core date and time systems needed to refactored. So we had no choice but to delay those add-ons. Our developers and support staff are actually working overtime to get these features developed, tested, and released ASAP. However, we’ve released a branch of EE4, for testing the promotions add-on, and the promotions add-on on our Github repository. You can find out more about getting access to the Github private repo, where we have the promotions add-on available for testing, here: https://eventespresso.com/developers/
Regarding this statement:
Can you please elaborate? We have customers that are processing upwards of 200 tickets at a time: https://eventespresso.com/topic/ee4-wp_esp_registration-reg_group_size-limit-per-transaction127/
I hope that helps. Please let us know if you have anymore questions.