Event Management UI Changes

[mkerc...@gmail.com]

Endpoint you called. Include the entire path. Be sure to redact your OAuth token as the group is a public page.

https://www.eventbriteapi.com/v3/events/71854736451/

Response you expected from the call.

The event details management UI (https://www.eventbrite.com/manage/events/71854736451/details) no longer contains a text area that populates the description.html property.

Response you received. Include the error message if you received one. If your response was missing data, please include the ID of the object you were expecting to see, but did not.

The description.html property is included, but it is always populated from the summary text area in the management UI.  We can no longer enter data in the management UI to populate this property.

Steps you have already taken to debug the issue.

The event detais management UI (https://www.eventbrite.com/manage/events/71854736451/details) changed recently to include new text boxes which are not returned by the API I'm using (https://www.eventbriteapi.com/v3/events/71854736451/).  I did discover that these new text boxes are considered structured data.  I understand that I can use a new API to reach into this structured data and return values, but this doesn't work for older events.

Overall goal you are trying to accomplish with your integration. This information provides the community an opportunity to suggest the best way to integrate with the API if your current usage isn't as efficient as it could be.

I've had a web hook set up for a couple of years now that is called when an event is modified.  It takes the unlimited length contents of the description.html property in https://www.eventbriteapi.com/v3/events/71854736451/ and consumes it for display within our UI.  I'd like to update the event details management UI (https://www.eventbrite.com/manage/events/71854736451/details) to restore the description text area so that the implementation continues working as it did in the past for both new events and existing events.

[gree...@gmail.com]

I second this, events created before the change seem fine but newer ones are returning the summary as the description.

[gree...@gmail.com]

After a few more minutes reading the groups, I found this thread:

https://groups.google.com/forum/#!searchin/eventbrite-api/summary$20and$20description%7Csort:date/eventbrite-api/GKUSYjPdxxc/P_ViAGu_EQAJ

So... it looks like you've got to make two API calls!

[Jacob]

Hey all!

Yes, green2go is exactly right. With the updates to our platform, the event description has become a little more involved than previously, and multiple calls are currently required to create an event description, as 

We've got updated documentation on the Structured Content and how to set your event description in the new interface ( https://www.eventbrite.com/platform/api#/reference/event-description) but we're still in the process of updating and improving that documentation so it's a little clearer for our users.

Hope this helps!

Best,

-Jacob

Eventbrite Developer Support

[mkerc...@gmail.com]

Is there a way to switch to the Classic Event Creation Experience either permanently or temporarily?  It would be nice to at least have some time time to change our web hook handler to support the new way to retrieve the event description via the API.

[Houston Krohman]

Yes this is something your account manager or sales rep can assist you with. If you are an SSO creator, you can reach out through our standard support channel to request this.

[mkerc...@gmail.com]

My goal is to update our web hook handler to call to the structured content api to get descriptions when the user created the event with the new event creation experience and not when the user is updating an event created using the classic creation experience.  I'm retrieving event information by event_id using the events API: https://www.eventbriteapi.com/v3/events/event_id/.  In order to achieve this I need to know which creation experience was used when requesting data from the API.

Is there a way to tell which event creation experience (classic or new) was used when requesting an event from the events API ()?  I found that an old event has source="create_2.0" and a new event has source="coyote".  Are these reliable values?  I can't find any documentation on the available values for the source values in the event api.  Is there another way to determine the creation experience used?

[perfecs...@gmail.com]