totemstech/instagram-node

Not possible to use both client_secret and access_token for requests

tom2strobl opened this issue · 2 comments

tom2strobl commented

Am I correct: The system assumes that you either use client_id + client_secret OR an access_token (eg in the use public function).

But if I want to sign my requests so I don't run into spamming algorithms as quickly (yup that's the case), I want to request with an access_token (to get 5k req's per user) and still need to send my app's client_secret for signing.

While it works by overriding client_secret manually at https://github.com/totemstech/instagram-node/blob/master/lib/instagram.js#L142 it's obviously dirty as hell and still throws errors on https://github.com/totemstech/instagram-node/blob/master/lib/instagram.js#L343

Do you have any advice for me?

camwes commented

considering the fact that all endpoints have to use an access_token the use function must be updated to allow for both in order to sign requests properly.

CelsoSantos commented

How are we on this?

Are there any changes to the lib that now support this behaviour?

  • 👍1