You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
I just noticed that the requests to Eventbrite are using headers for authorization. Do the requests to Meetup's API not require any headers for the sake of authorization?
I bring this up because when I go to the Meetup API endpoint that's used in App.py I get this output: {"errors":[{"code":"auth_fail","message":"Invalid csrf credentials"}]}
The text was updated successfully, but these errors were encountered:
I believe we changed the URLs to use the v3 API, but since we're only doing GET requests which are publicly available, I don't think we needed to setup OAuth to make those base requests.
Do you think something you were doing was hitting a v2 API OR trying to pass the &key= GET parameter which is now deprecated? We were using key={a value from config.ini} but we simply removed it and started using v3 public GET requests.
I just noticed that the requests to Eventbrite are using headers for authorization. Do the requests to Meetup's API not require any headers for the sake of authorization?
I bring this up because when I go to the Meetup API endpoint that's used in App.py I get this output:
{"errors":[{"code":"auth_fail","message":"Invalid csrf credentials"}]}
The text was updated successfully, but these errors were encountered: