getting selective fields from the event APis

[Boloramji]

Is there an easy way to get selective fields in the response object
rather than the entire object and then selectiing the fields?
Currently, for example, http://api.meetup.com/2/events gets too much
information many of them are not necessary in most requests. If we can
pass the parameters like example
http://api.meetup.com/2/events/?key=&fields=id,time,name
then we can just get those fields there by reducing the traffic
If not there, is it possible to add to the enehancement queue?

Thanks

[Doug Tangren]

This is something I have been thinking about and may be more of a candidate for features in the v3 api. The "fields" request parameter is already taken. Fields represents the optional response properties left out which can incur extra query overhead. Things get a little more complicated when you have nested objects in responses. In that case, you have to come up with a format that describes which object you are intending the field to be populated in. This needs a little more thinking in terms of architecture and design but I'm glad to see you have expressed interest in the idea. The more interest we see in features, the more likely we are to implement them.

[Shreyas Dube]

+1 interest

--
Ray

[Steven]

+1

Not sure why the Venue information is returned with every 2/rsvps response.
Since the API is limited to the specific events requested the venue information is redundant.

If one could say "give me all the RSVPs" for a specific member then it would not be redundant.

[Doug Tangren]

You can pass in multiple event ids which each could have varying venues, http://www.meetup.com/meetup_api/docs/2/rsvps/#params

The only parameter that will cause the response data to change for a given method is the "fields" parameter for adding extra optional properties. We do have our agenda providing support for a way to do the opposite, removing target properties.

 

--
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

[Steven]

On Monday, March 5, 2012 10:07:46 AM UTC-8, Doug Tangren wrote:

On Mon, Mar 5, 2012 at 11:27 AM, Steven wrote:

Not sure why the Venue information is returned with every 2/rsvps response.
Since the API is limited to the specific events requested the venue information is redundant.

If one could say "give me all the RSVPs" for a specific member then it would not be redundant.

You can pass in multiple event ids which each could have varying venues, http://www.meetup.com/meetup_api/docs/2/rsvps/#params

The only parameter that will cause the response data to change for a given method is the "fields" parameter for adding extra optional properties. We do have our agenda providing support for a way to do the opposite, removing target properties.

I guess my  thought on this is that to get one or more event IDs to place in the 2/rsvps call you (most likely) did a 2/events or similar fetch and that returned the venue information so returning the venue information with each of up to hundreds of RSVPs is inefficient.