-
Notifications
You must be signed in to change notification settings - Fork 6
Requests to Meetup API are missing headers #40
Comments
@ramonaspence check out this old issue about Meetup v2 vs v3. 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. |
Oh I see. So, it was actually an invalid "group name" that I was giving the url.
So no issue with the headers then. |
Nice. Do we need to keep this issue open, or is it good now? |
We're good now 👍🏻 |
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: