Supposed to use key= not sig=

[rickm...@gmail.com]

I (half) answered my own question from the previous posting.

As a new member to this list, I didn't see my posting up right away.

Have to find out if the moderator likes me.

Anyway, I realized that I should just search this group for any examples

using curl. Guess I should have done that first thing. So, I got my answer:

$ curl "https://api.meetup.com/2/members.json?key=123&group_urlname=HackerNest"

... assuming my key is 123. But using "...?sig=123..." is the wrong thing to do.

But that still doesn't explain why this example fails:

$ curl -H "Authorization: Bearer {123}" "https://api.meetup.com/topics?page=1"

Don't care too much anymore because I have that "members.json?key=123" example.

Although if you could tell me why that Authorization Bearer line is wrong, then I'll learn something else.

[Doug Tangren]

The authorization header in this case expects a bearer token from one of our oauth flows. It doesn't support api keys at the moment.

 

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.