New Instagram API restrictions & how it affects Instafeed.js

[goldprismco]

UPDATE (@stevenschobert): This thread has turned into a conversation about how Instafeed.js is going to work with Instagram's new API restrictions.

Currently, new Instagram API clients are not able to fetch much of the data that Instafeed.js relied on to work, and we are evaluating options for how to handle authentication going forward. Credentials created before the API restrictions went live are not affected for now.

---

Original Post:
I'm working on a client project (built on Shopify platform) and am looking to pull in their Instagram posts by user. I have it all setup - but it will not pull in my client's account. When I plug in my personal Instagram account userId & clientId, everything works perfect so I know it's not an issue with how I have it set up. Are there any known security settings that will prevent instafeed from working on a specific account? To note, the account I'm looking to pull in has a very large following.. not sure if that has anything to do with it?

Here's the set-up I have for reference (includes liquid language as used on Shopify, so just ignore that):

{% assign instafeed_img = '{{image}}' %}
{% assign instafeed_link = '{{link}}' %}
{% assign instafeed_likes = '{{likes}}' %}
{{ 'instafeed.min.js' | asset_url | script_tag }}
<script type="text/javascript">

var userFeed = new Instafeed({
    target: 'instafeed',
    get: 'user',
    userId: '260149935',
    clientId: 'xxx',
    limit: '10',
    sortBy: 'most-recent',
    resolution: 'standard_resolution',
  template: '<div class="grid__item large--one-fifth"><a href="{{ instafeed_link }}" target="_blank"><img src="{{ instafeed_img }}"><span class="likes"><span class="icon icon-heart" aria-hidden="true"></span>{{ instafeed_likes }}</span></a></div>'
});
userFeed.run();
</script>

[goldprismco]

UPDATE! Not sure why but with my client's account userId & clientId I'm getting an error: "The access_token provided is invalid". There's no access_token provided in the script, or course, as it was noted that with the recent version of instafeed this is no longer required. This error does NOT come up when I have my personal Instagram userId & clientId plugged in (and the script works and pulls in my user feed).

Thanks in advance for any insight you can provide on why this is happening & how to fix.

[123ndy]

I am also having this problem (with plain js). When I create a new Instagram client and provide the CLIENT_ID into instafeed, I get "The access_token provided is invalid". When I use a random CLIENT_ID I found on some forum, it works. I have tried with two different CLIENT_IDs I found on some forums and they both work, but none of mine newly created CLIENT_IDs work?

[stevenschobert]

This is most likely due to the new API restrictions Instagram rolled out this week:
http://instagram.com/developer/changelog/

Have either of you tried to submit your new client apps to the review process?

[123ndy]

That would explain it. I will get the client app reviewed, and report back.

[stevenschobert]

@goldprismco @123ndy Just a quick update:

I tried creating a new Instagram client ID and received this same error. I'm currently waiting to submit a test application through their review process. I'm hoping they will accept it under the "share my own content" use case, but we'll have to see!

Sorry for the inconvenience folks, I wish there was something more I could do 😞

[123ndy]

Seems we have to wait untill Dec 3, 2015 before they start to accept Permissions Review submissions.

[goldprismco]

@stevenschobert thanks for looking into it! Would using the access token fix this in the interim?

[stevenschobert]

@goldprismco If the token was generated before the API restrictions went into place, then it might. The same goes for client IDs.

My current understanding is that all new API credentials (including both access tokens and the client IDs they belong to) are now stuck in sandbox mode until the review process opens up.

[iljapanic]

I'm having the same issue. Token from the old API works without any issues, however the newly generated tokens don't work.

Any suggestions on how to go about solving this?

[123ndy]

@iljapanic I think we just have to wait until Dec 3 when they start to accept Permissions Review submissions.

[egardner]

I'm experiencing the same issue as well. Hoping that the Instagram API changes don't make it impossible to continue using the script in this fashion.

[bakura10]

Ouch, that sounds like a major pain change from Instagram. We were using that for Shopify too, where customers can simply enter their client ID, but I started to receive mails from people saying it does not work.

If we now must explain them that they should submit their app and wait, it will definitely be very annoying. Did anyone try if the access token suffers from the same issue?

[bakura10]

It seems though that access token retrieved from the Instafeed client (https://instagram.com/oauth/authorize/?client_id=467ede5a6b9b48ae8e03f4e2582aeeb3&redirect_uri=http://instafeedjs.com&response_type=token) properly returns an access token that seems to work (at least that's how we recommend our theme customers to get their token and so far I didn't receive any email saying that it does not work). Asking our customers to create a client, asking permissions, justifying permissions, waiting... does not seem possible tbh.

So maybe Instafeed may make sure that their client used to generate those tokens is properly being reviewed so that it can continues generate token in the future?

[stevenschobert]

Update: I submitted an application for review to Instagram earlier today, and am waiting to hear back.

I did discover that sandboxed clients can still access limited user information (if the user has been invited to the sandbox app), but only through access tokens, and only the last 20 pictures. This in theory would allow Instafeed.js to continue, but severely limits its usefulness :(

Hoping for the best everyone! Please accept my apologies, I wish there was more I could do to change the situation!