Eventbrite.com Events API Bot #217

Activity

1. allella

   added

   enhancementNew feature or requestNew feature or request

   and removed

   enhancementNew feature or requestNew feature or request

   on Feb 8, 2018
2. allella commented on Feb 19, 2018

   

   allella

   on Feb 19, 2018

   MemberAuthor

   More actions

   @Nunie123 not sure this will mess with anything but
   https://data.openupstate.org/organization/hubspot-users-group

   has changed from Meetup to Eventbrite. Figured I'd mention it in case something goes goofy when changing services.

   https://www.eventbrite.com/o/greenville-hug-16473566371
3. Nunie123 commented on Feb 23, 2018

   

   Nunie123

   on Feb 23, 2018

   More actions

   None of the groups are hardcoded on the API end, so as long as the provided API key is correct it'll show up. Thanks for the heads up.

   👍React with 👍1Reacted by Jim Ciallella
4. allella commented on Feb 28, 2018

   

   allella

   on Feb 28, 2018

   MemberAuthor

   More actions

   Check it out.

   

   🎉React with 🎉2Reacted by Glen K. Peterson and Adam Hodges
5. allella

   assigned

   allella

   and unassigned

   allella

   on May 6, 2020
6. allella commented on May 6, 2020

   

   allella

   on May 6, 2020

   Last edited by allella

   MemberAuthor

   More actions

   @ramonaspence @bcsnipes

   A few more notes about Eventbrite's v3 API

   Eventbrite uses OAUTH tokens.

   For our current use case, we only need each developer to generate a personal, private token
   https://www.eventbrite.com/platform/api#/get-a-private-token

   We're not trying to make API requests on behalf of other Eventbrite users, so the "(For App Partners) Authorize your Users" is currently not needed.

   There's this API test tool, similar to Meetup's API browser tool, but this one seems a bit harder to navigate. Also, you need a token to authorize and authenticate.
   https://www.eventbriteapi.com/v3/events/10584525601/?token={INSERT YOUR API PRIVATE TOKEN HERE}

   Not sure we ever used this, but "search events" is deprecated as of Thursday, December 12, 2019. and replaced by List Events by Organization — GET /v3/organizations/:organization_id/events/

   Our application currently uses
   https://www.eventbriteapi.com/v3/organizers/{organizer_id}/events/

   I have concerns this API endpoint is going to be deprecated because it's not listed in the API Reference and similar endpoints, like GET /v3/organizers/, are listed in the change log for removal in June 2020.

   Here is an example for Tech After 5 when called from a browser
   https://www.eventbriteapi.com/v3/organizers/444331701/events/?token={YOURAPIPRIVATETOKENHERE}

   However, this response is paginated with a limit of 50 events per page. So, once an organizer has [more the 50 events it would require using a continuation token].(https://www.eventbrite.com/platform/api#/introduction/paginated-responses/what's-in-a-paginated-response?) Since this application typically doesn't need all the old events, so it will be easier to limit the results to only future, or very recent events.

   Specifying a start_date.rage_start=2020-05-01T23:00:15Z will only show future events after that date. Sorting by the start date, descending would also partially avoid the need to paginate in our application order_by=start_desc

   It's also possible to filter based on status and a few other parameters
   

   https://www.eventbriteapi.com/v3/organizers/444331701/events/?start_date.range_start=2020-05-01T23%3A00%3A15Z&token={YOURAPIPRIVATETOKENHERE}

   Eventbrite's API has a limit of 2000 API requests per hour, per token. The HTTP response headers will include a "X-Rate-Limit" header with the current count and how many seconds until the count will reset.

   X-Rate-Limit: token:{YOURAPIPRIVATETOKENHERE} 31/2000 reset=1962s, key:SOMEKEYVALUE 31/2000 reset=1962s

   Error logging notes, mostly for my own future reference

       import sys
       from pprint import pformat
   
       # logger.error("-------");
       logger.error(pformat(data.get('events')));
       logger.error("-------");
       # logger.error(events);
   
       sys.exit()
   
7. allella commented on Mar 18, 2021

   

   allella

   on Mar 18, 2021

   Last edited by allella

   MemberAuthor

   More actions

   Posting an example requesting an organizer / organization and then of its events, for future reference.

   You'll need to apply a valid token on the end, which can be registered using the link on the Eventbrite testing tool.

   All upcoming events for Tech After 5
   https://www.eventbriteapi.com/v3/organizers/444331701/events?token=**YOURTOKENHERE**

   Organizer info for Tech After 5
   https://www.eventbriteapi.com/v3/organizers/444331701/?token=**YOURTOKENHERE**
8. github-project-automation

   added this to HackGreenville Labs - Good First Issueson Jan 25, 2024
9. github-project-automation

   moved this to Todo in HackGreenville Labs - Good First Issueson Jan 25, 2024
10. allella

    transferred this issue fromhackgvl/events-apion Jan 25, 2024
11. allella commented on Jan 25, 2024

    

    allella

    on Jan 25, 2024

    MemberAuthor

    More actions

    Transferred this issue from the old Events API.

    We only left this open because it had some helpful notes and examples on how to interact with Eventbrite's API.
12. allella

    closed this as completedon Jan 25, 2024
13. github-project-automation

    moved this from Todo to Done in HackGreenville Labs - Good First Issueson Jan 25, 2024
14. allella

    removed this from HackGreenville Labs - Good First Issueson Aug 6, 2024