Meetup API Client v1.0.0

  • PHP
  • March 29, 2013

I love APIs, but I honestly hate having to deal with signing, auth, and curl inside my controllers or services, which means I end up wrapping all of that into something that provides easy access in my controllers. I also love Meetup.com since it really makes managing User Groups pretty cool, even with some bad UI choices, which is exactly where their API comes in, it allows me to provide a decent interface to their features from my own UG page and do all the communication via API.

I was curious about the Guzzle library and how many people mentioned it would make API wrapper so much simpler, so I decided to put all of those together and write my own wrapper that would have complete support for the API (other wrappers only had read-only).

It was a simple process, I prepared 2 basic clients to deal with the auth options available: key auth and OAuth. This was pretty simple with the use of Plugins and the existing OAuth plugin. Next up I tackled the operation definitions, for which i ended up with a screen scraper that would get me most of the information from the Meetup.com Docs, and tweak it from there.

Once the definitions were done I started testing out my use cases and realized that always having to read the ‘results’ item of the response array was tiresome and led to useless code, so I wrote a few custom responses that allow me to directly iterate or access the data with array access and iterators. This proved to be useful and my use cases became much more simpler on the consumption side.

To this I also added a ‘__call’ method that can call any operation and generated proper phpDoc for each method so that IDE’s can easily provide autocomplete for this.

This is a sample of it in action:

 <?php

$client = MeetupKeyAuthClient::factory(array('key' => 'my-meetup-key'));

// Use our \_\_call method (auto-complete provided) $response = $client->getRSVPs(array('event\_id' => 'the-event-id'));

foreach ($response as $responseItem) { echo $responseItem\['member'\]\['name'\] . PHP\_EOL; } 

This has been very useful for AmsterdamPHP since we use the Meetup API heavily and I hope its also useful to more people using that API, installation is also pretty simple since it supports composer, and a Symfony Bundle is in the works. If you want more details go check out the github repository and its README file. Or check it out on Packagist .

comments powered by Disqus

Related Posts

Problem solving technique #1: Taking a mental break

Problem solving technique #1: Taking a mental break

  • February 4, 2011

Developers are modern day artists whose masterpieces are not hung on walls but stretched out thin on web servers all over the world, yes that is very poetic, but I really try to look at developers as artists and puzzle solvers.

Read More
Rails: Segmentando CSS por telas

Rails: Segmentando CSS por telas

  • September 12, 2008

Sites muito grandes acabam por ter arquivos CSS enormes, e que mesmo divididos em várias partes e utilizando @import, são carregados em todas as páginas e podem causar atraso no carregamento de páginas.

Não seria ideal que, por exemplo, nossa página de login possua uma folha de estilo própria, mas que este CSS seja carregado apenas quando estivermos na página de login? Seria, e é isso que vou abordar neste artigo, um pequeno mas útil truque, que aprendi em um dos videocasts da Railscasts.com .

Read More
PHP Conference Brasil 09 - Quarta

PHP Conference Brasil 09 - Quarta

  • November 25, 2009

Um dia e meio antes da iniciar oficialmente a conference deste ano, começo meu relato sobre o dia a dia da conference em formato de video, seguindo os exemplos de nomes como Cal Evans e Eli White.

Read More