Event Espresso 4 REST API Survey

In an ongoing effort to bring WordPress developers and event managers the tools they need to manage their event businesses, we are asking for feedback from Event Espresso & WordPress development communities, about their experience with our Event Espresso 3 JSON API, as well as any other API they’ve used in the past.

Please share your experiences, using the form below. Your feedback will help us steer the EE4 REST API development in the right direction.

Name
First Last
Email
Website
REST APIs make EE4's data available to applications not hosted on your server. What have you done or would you like to be able to do with the EE4 REST API?*
We would like to know what use cases you have, so we can make those common use cases easier.
If you are a developer, what are some aspects of other APIs that you would like to see in EE4's REST API?*
If you plan on using the API for getting EE data, describe what kinds of queries (in english) you might like to run.*
Eg.: “Get all events for in Kansas city”, or “Get all payments made in January for the event ‘Star Wars Conference”. We want to get an idea for how complicated the queries developers will want.
If you plan to CREATE and UPDATE EE Data using the API, what data do you plan on creating/updating?*
We want to know what are the most important things for developers to ADD/UPDATE in the database.
If you plan to CREATE and UPDATE EE Data, would you rather use a low-level API (where your code would have more complete control over the data, but would need to take care of ensuring data integrity, triggering messages to be sent, and generally duplicating EE core’s behaviour) or a high-level API (where you wouldn’t have as much control over the data, but our code would take care of making sure the data remains consistent, our code would trigger messages, and make sure the API behaves like normal EE).*
We want to know which users value more: control over the data, or simplicity of development.
Have you used the Event Espresso 3 JSON API?*
If you are a developer, were there any parts of using the EE3 JSON API that were especially useful?*
What EE3 JSON API features were of most use?*
We want to know, if a particular feature, or endpoint was dropped from EE4 REST API, what would you be most upset about losing?
If you are a developer, were there any parts of using the EE3 JSON API that were frustrating?*
GDPR Agreement*
- I consent to have this website store my submitted information so they can respond to my inquiry.
Comments
This field is for validation purposes and should be left unchanged.