This long-polling stream can be easily consumed using JavaScript in any modern browser. Checkin notifications are received when they happen, or as soon as your script finishes handling its last notification.
These parameters are set automatically by Meetup's must.js client.
Checkin notification objects include these properties. This method's response is an array of zero or more of these, while Meetup's JS client calls your callback function with exactly one object.
For browsers that support it, WebSockets is a more efficient alternative to the long-polling stream. This is a push only endpoint and will discard any messages received from the client after the socket is open.
Because browser support for WebSockets is limited, we recommend that you consume this stream through the must.js client, which can fallback to long-polling.
The full URL for this method is ws://stream.meetup.com/2/checkins
This stream includes the same JSON notification objects as its long-polling counterpart, one per WebSocket frame.
This method serves checkin notifications using chunked encoding to maintian a persistent connection with a client. The connection will only be terminiated for server maintenance or a connection error. It is suitable for low-level HTTP clients rather than web browsers.
This stream includes the same JSON notification objects as its long-polling counterpart. These are served one per HTTP chunk and terminated by newlines.
Try out the checkins stream on the command line
curl -i http://stream.meetup.com/2/checkins
Meetup members, Log in
By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy
everywhere comments