I have many Instagram accounts for which I want to update the profile photos remotely. I am not the account owner for each so signing in with an OAuth password screen is not the best option as I will not have access to each account’s password.
Are either the OAuth2 Custom Token or JSON Web Token the best option here (or something else)? In my scenario, I would request permission from the account owner to update the profile via API call. They would grant it and I would gain access via token then could submit the update to the profile photo. Then after 24 hours I would lose my ability to make any changes.
oAuth2 client_credentials if available (in Bubble, this is using custom token).
JSON Web Token is different from a service to another and can be hard to make it work in Bubble API Connector (and sometimes very simple because this is used in a header authorization).
But… I’m not sure that Instagram API offer this kind of service…
And when I read this:
This really sound like an oAuth2 authorization code flow (user-agent called in Bubble). Each account owner should use instagram to login to your app
Is it an extra work to A) login using oauth2 VS b) create and send you API token keys? (if service offer this option for client credential or JSON webtoken, or even just an API key)
If a lot easier to account owner to just login to your service VS create token
Hmm, I should rephrase that. The account holder would not interface with our app at all ideally. Perhaps I need to think of a more user-friendly way for them to say “sure, here’s my password, have at it”. The way I envisioned it was like granting edit access to a Google Sheet.