Please have a look at this http://stackoverflow.com/questions/37328957/meetup-api-scroll-parameter-broken
--
--
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.
On Monday, 23 May 2016 06:32:16 UTC+2, Doug Tangren wrote:On Thu, May 19, 2016 at 12:48 PM, Alessandro <alessand...@gmail.com> wrote:Please have a look at this http://stackoverflow.com/questions/37328957/meetup-api-scroll-parameter-broken--Hi Alessandro,The Meetup API defines two supported values ( http://www.meetup.com/meetup_api/docs/:urlname/events/#listparams ) which users may supply for the scroll parameter. "next_upcoming" and "recent_past". Server generated values, like the one your referencing should be considered opaque strings. Can you let us know what the payload of the 400 error looks like? It should contain a code and a message describing the error.--
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.
--
Good to hear, Doug! May I follow the progress for this fix somewhere apart this group?
On Thu, May 26, 2016 at 12:42 PM, Alessandro <alessand...@gmail.com> wrote:Good to hear, Doug! May I follow the progress for this fix somewhere apart this group?I'll post a message here with the fix goes live