api - single client_id vs. user authorization for showing multiple instagram feeds on a website -


i'm developing of community website features 500 user profiles. want add option show users' instagram feed on profile (with consent). going through instagram api documentation questions arose concerning right approach permissions , review process.

can clarify if following working approach , valid use case regarding instagram's policy: creating 1 client id / access token website used communicate serverside instagram api, using public_content permission query members' timeline. server side caching ensure rate limits respected.

since need read-only access public content avoid managing authorization of every single member.

thanks!

in recent api changes instagram removed ability use client_id requests , access_toek obtained authorising , instagram account required everything

you make account website, authorize , use access_token, need apply public_content permission , don't thin instagram use case. 500 accounts may hit ali request limit.

the better option require uses authorise instagram account if want recent posts on profile , use token recent posts. way don't need public_content permission


Comments

Popular posts from this blog

java - Jasper subreport showing only one entry from the JSON data source when embedded in the Title band -

serialization - Convert Any type in scala to Array[Byte] and back -

SonarQube Plugin for Jenkins does not find SonarQube Scanner executable -