I'm confused. ```Instagram.options[:access_token]``` is set upon the initial client creation, so wouldn't that be what is used for the call to ```next```?

Are you raising a case where there may be multiple Instagram clients acting in an application, each with their own access_token, and  interleaving calls between them would cause problems?

Agreed that passing the client object is a better approach. I didn't want to "break" the current architecture, which is based on one-request/one-response. I couldn't come up with a seemingly good way to share the client object internally.