On the 17 Nov 2015 Instagram made changes to their API. Apps created before Nov 17, 2015 wont be affected until Jun 2016. Apps created on or after Nov 17 2015 will require to use their updated API. Please note that this library doesn't yet support their new updates.

When we launched our first Instagram API in 2011, we were a very small team and knew we wouldn’t be able to build all the features our community might want. Today we are announcing several platform changes to improve people’s control over their content and set up a more sustainable environment built around authentic experiences on the platform… http://developers.instagram.com/post/133424514006/instagram-platform-update

I guess we need to rethink this entire library in order to work with the latest changes. This will require a lot of efforts and there is currently no plan to update this library.

If you're just looking for a simple way to fetch a public Instagram feed, you can checkout this package: vinkla/instagram.

There is a new security mechanism in town:

http://developers.instagram.com/post/116410697261/publishing-guidelines-and-signed-requests

Don't know, if the old system with signed headers is fully deprecated.

Documentation of the feature: https://instagram.com/developer/secure-api-requests/

Hello excuse me. my English writing is bad. i need a forced SIGNED key that have permission of like. instagram policy have been changed. and new public app can not access to like endpoint. Link(http://developers.instagram.com/post/116410697261/publishing-guidelines-and-signed-requests) do you have any key with permission of like? i can buy it from you .( or i can give 15% of my sell to you .) if you give me a key with like permission

i promise you that i use it only in my application. and my application is valid in (TERMS OF USE) of instagram.

please reply to my message for more speeking about it.

thanks.

Hi, I've been using your instagram API and thanks for putting it up.

Now I'm working at the stage where I can follow/unfollow users.

However when I tried the simple example given

$instagram->modifyRelationship('follow', 1574083);

it doesn't work.

do you mind showing me how your modifyRelationship func works?

Cheers.

Hi, I've been working with your wrapper for a while now (thanks so much for it!) and I've been trying to figure out a pagination method but couldn't figure it out! the example you used in the docs don't work either... the $instagram->pagination()...

Any ideas?

Hi Christian,

Good job on this class!

A few thoughts on the alpha pagination method.

We found that the current method was quite restrictive because you're having to pass the entire response from a previous call.

Instead, would it be better to just be able to pass the next_max_id into the method?

So the PHP method would simply be like this (Ignore the naming convention)

  public function paginationById($next_max_id) {
    if (true === is_int($next_max_id) ) {
      return $this->_makeCall($function, $auth, array('max_id' => $next_max_id));
    } else {
      throw new Exception("Error: pagination() | Pagination doesn't support this paramater type.");
    }
  }

When calling the instagram API, you're limited to 5000 calls per hour per token. It would be very useful if your class/code had an attribute that stored that info so I could keep track of where my users are in their current hour's limit.

Is there a call to be made that will give the current limit without expending 1 call? Doesn't seem like it.

I successfully can get the media by tags with my access_token using link at below:

(https://api.instagram.com/v1/tags/qe/media/recent?access_token=MY_TOKEN)

But, while using this api, i receive an error: The access_token provided is invalid

Here is my code:

$instagram = new Instagram($client_id); //
$instagram->setAccessToken($my_token);
$tags = $instagram->getTag("qe");

What is wrong in my code?

Recent updates to the API require that count > 0 when calling search/user. Current code documentation suggests that $limit is optional, but the default $limit value is always passed to the API regardless. Since the API now won't accept 0 as a valid value, it returns an error. To maintain backwards compatibility, this change passes the count value to the API if and only if it has been explicitly set when calling searchUser().

This same pattern (unspecified $limit then turning into an explicit value for count when calling the API) exists for a number of other methods as well. To maintain consistency, the other affected methods which take $limit as an "optional" parameter have been modified to follow the same convention.

When I try running the example in my wamp localhost I get: ( ! ) Fatal error: Uncaught exception 'Exception' with message 'Error: _makeCall() - cURL error: Problem (2) in the Chunked-Encoded data' in C:\wamp\www\insta\example\instagram.class.php on line 454 ( ! ) Exception: Error: _makeCall() - cURL error: Problem (2) in the Chunked-Encoded data in C:\wamp\www\insta\example\instagram.class.php on line 454

If I comment out the line that throws the exception above I'm then greeted by this: ( ! ) Notice: Trying to get property of non-object in C:\wamp\www\insta\example\success.php on line 68 ( ! ) Warning: Invalid argument supplied for foreach() in C:\wamp\www\insta\example\success.php on line 68

I've already added these to lines to the _makeCall function: curl__setopt($ch, CURLOPT_SSL_VERIFYPEER, false); curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);

Any help would be much appreciated.

This is my first time working with cosenary. So far, good. But when I try to autenticate access some private methods I receive "Notice: Undefined property: stdClass" when I call "setAccessToken". Here is some sample code:

Any help?

Thanks

Hey there!

I'd like to report a security issue but cannot find contact instructions on your repository.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

https://huntr.dev/users/Mik317 has fixed the Cross-site Scripting (XSS) vulnerability 🔨. Mik317 has been awarded $25 for fixing the vulnerability through the huntr bug bounty program 💵. Think you could fix a vulnerability like this?

Get involved at https://huntr.dev/

Q | A Version Affected | ALL Bug Fix | YES Original Pull Request | https://github.com/418sec/Instagram-PHP-API/pull/2 Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/packagist/instagram-php-api/1/README.md

User Comments:

📊 Metadata *

Bounty URL: https://www.huntr.dev/bounties/1-packagist-instagram-php-api

⚙️ Description *

An XSS issue occured in the instagram-php-api project, which was due to insecure reflection of usersupplied input through the ?error_description parameter.

💻 Technical Description *

I used the htmlentities() method to sanitize the malicious parameter, avoiding the issue aforementioned.

🐛 Proof of Concept (PoC) *

No POC, but the issue was clear by the code

🔥 Proof of Fix (PoF) *

No POC, but htmlentities() works fine with every scenario

👍 User Acceptance Testing (UAT)

Just used htmlentities() on a string

Based on the breaking changes of the Instagram API on June 29, 2020:

The remaining Instagram Legacy API permission ("Basic Permission") was disabled on June 29, 2020. As of June 29, third-party apps no longer have access to the Legacy API.

More info here: https://www.instagram.com/developer/

@cosenary, this library is no longer working.

i took app_secret key and app_id, wrote this codes but when i clicked Login with instagram, i take 'Oops, an error occurred.' error in page.

help please.