Ah that's true. My thinking was to make it more similar to their [Twitter example][1] which feels a lot like a [full on wrapper][2] but being nice and general. I totally agree on the headers though, wasn't thinking about multiple APIs being used together. Would a subclass make sense? I'm thinking that later we can incorporate the use of methods for resources and using the class for namespacing and inheriting the headers/base_uri, like: `Storyteller::Twitter.timeline`.

[1]: https://github.com/jnunemaker/httparty/blob/master/examples/twitter.rb
[2]: https://github.com/sferik/twitter