Skip to content

Instagram unable to connect - Invalid scope: user_profile / Deprecated API #586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
petar-staynov-brandwatch opened this issue Feb 17, 2025 · 4 comments

Comments

@petar-staynov-brandwatch

We're using filestack-js in our Angular application however as of recently we've started experiencing issues when trying to connect to Instagram. It seems there has been an update to Instagram's API in December and the Instagram Basic Display API has been deprecated which seems to be the cause as mentioned in other online resources.
https://developers.facebook.com/community/threads/564807592825106/

https://developers.facebook.com/blog/post/2024/09/04/update-on-instagram-basic-display-api/

Steps to reproduce:

  1. Open Filestack
  2. Select Instagram -> Connect Instagram
  3. Instagram page opens and shows error Invalid request: Request parameters are invalid: Invalid scope: user_profile

Test conditions
Tested in Chrome 135
filestack-js version 3.37.5

@ubaniabalogun
Copy link

Also seeing the same issue. Can we get an updated please?

@Bagratfilestack
Copy link

HI @petar-staynov-brandwatch , @ubaniabalogun

This issue started because Meta removed the API scope from their side and now they dont allow it to be used. You can check more here.
https://developers.facebook.com/blog/post/2024/09/04/update-on-instagram-basic-display-api/

The only option left is to change the API scope and use the one that will work only for the business accounts, so only the users who have a business account will be able to pass the authentification and get the data from Instagram. Which we believe will not be useful for you as well.

@ubaniabalogun
Copy link

@Bagratfilestack am I understanding correctly that your team does not have a resolution or workaround for this issue?

@Bagratfilestack
Copy link

@ubaniabalogun its not that our team has no resolution or workaround. The thing is that the only provider of the access is Meta and they have blocked it. None of the providers will be able to allow this until Meta decides to open it back. We are trying to work with them to find a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants