Workaround for new Instagram API restriction for tagged content - api

I built a module for my company's marketing team to fetch all the photos based on a hashtag. Such as #nofilter.
I was using the URL https://api.instagram.com/v1/tags/nofilter/media/recent with no problems until Instagram decided to change their API authentication to OAuth.
I followed the new guidelines but my client is still in sandbox mode and the API call doesn't return anything anymore. All it returns is:
{"pagination": {"deprecation_warning": "next_max_id and min_id are deprecated for this endpoint; use min_tag_id and max_tag_id instead"}, "meta": {"code": 200}, "data": []}
It seems like I need to submit my application to be reviewed before going live. But this doesn't seem possible, based on what i found from their submission guideline below. Is there any workaround for this?
====== UPDATE July 8th, 2016
I have found one of those 3rd parties that instagram mentioned, but the pricing is awful https://www.dialogfeed.com/pricing/
189 euros per month seem a bit steep

I had to deal with this. Their documentation is pretty unhelpful and doesn't seem to offer any solution for someone just wanting to collect relevant links, which should be no prob.
Fortunately, the script on an Instagram page provides easy access to their structured data. In my rails app I create a headless browser and just hit their url. I provided my solution as an answer to another question:
https://stackoverflow.com/a/38572893/4888422

Related

Is there any way to post updates in a business location using google's business api?

As the title says, I'm trying to find a way to post these updates (see picture below) using google's API, I can't find anything about it. I have checked google's business API documentation and most of it's endpoints are deprecated.
At the top of the page there is a deprecation schedule: https://developers.google.com/my-business/content/sunset-dates
There you can find the new API-Endpoint. I'm also looking for a solution to update opening hours, but it's not that easy to find any information. Even bing is better documented.

Google Books API Branding Compliance issue--infoLink returns "Not found" page

I'm working with the Google Books API and the Branding Guidelines state that I have to have a prominent link to the Google Books page for each search result. Cool, I'm fine with that.
However:
saleInfo.buyLink isn't always there in the API response
volumeInfo.infoLink and volumeInfo.canonicalVolumeLink sometimes often go to a "Not Found" page (for example this page, which is supposed to have information for "Lunar Orbiter State Estimation Using Neural Network-based Crater Detection" by Lena Marie Downs [don't ask, I used faker to call the API with random keywords and picked a random result])
So my question becomes, is it my responsibility to try to find workarounds for any of that, in order to be compliant? Or should I just go with what Google Books gives me and call it a day?
I changed my seeds file to only look for Google Books that have an ebook available with &filter=ebooks, and I haven't run into these issues with what it found this time. But I guess the question still stands whether it's up to developers using the API to provide for Google's issues, in case anyone else wants to answer.

Deprecation of https://www.googleapis.com/plus/v1/people/me and how properly to migrate

Recently Google plus is pending for shutdown, which also shutdown some Google Plus API including this one https://www.googleapis.com/plus/v1/people/me which our service is actively using.
That above API was used in one of our legacy login library, which I can't even find the source for it. Hence I am now trying to patch it myself.
Reading the migrate guide from Google, it doens't tell much in terms of how to change the url.
Referencing some open source library like 1, 2. I have come up with the fix of replacing the url https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo, which works but oauth2/v3/userinfo lacks documentation, so I am pretty worry that oauth2/v3/userinfo is not intended to be used like the above.
So my question is:
Is my solution: change https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo an intended migration, if not then how can I migrate out of Google Plus API?
Any documentation on https://www.googleapis.com/oauth2/v3/userinfo? The closest I can find is this, which seems more like an brief intro then a documentation.
The "/oauth2/v3/userinfo" call will not be deprecated on March 7th, 2019 as it is not part of the Google + API.
If you look at the Google Developers Console, those calls are not registered as part of the Google + API.
From Google email:
If you are directly requesting the “plus.me” scope, any other Google+
OAuth scopes, or making any Google+ API calls, please ensure that you
remove these requests from your project before March 7, 2019.
Since nobody answer, I think I will give out the best info I can gather...
For 1. Supported by multiple open source project. Pac4j, hybridauth. It seems like the method of change https://www.googleapis.com/plus/v1/people/me with https://www.googleapis.com/oauth2/v3/userinfo is the best you can do to fix this issue.
For 2. Still no detail documentation for that

I'm trying to use Instagram API

I'm using default Instagram API, but when I try to fetch comments on posts, I'm getting a response with data empty, even when I know that there are comments on the post.
https://www.instagram.com/developer/endpoints/comments/
So when I tried to report it, it told me to migrate to Instagram Graph API. I searched, its look it's for personal use for business, I was building a raffle website helper, randomly pick a winner from a comment, and this broke my project.
Edit 1
So I'm confused because when I access Instagram Developer website says to gonna to new Instagram Graph API, but here, I got a message that it's just for business accounts, but I already have registered my app with "facebook login" like the links you have sent to me
See demo what I'm building: https://youtu.be/DmVN5t0dRaY
The problem: https://imgur.com/a/YHC5lZE
This is deprecated by Instagram. It's not really telling you to use the Graph API, it's saying that this is the way they are going and the Graph API is intended for business that want to maintain their own page and interact more successfully with Instagram users.
Instagram still offers an endpoint
GET /users/self/media/recent
That should suit your needs.

instagram retrieve hashtag images - update June 1

I am aware of the update to Instagram apis. I have read through the documentation regarding fetching hashtag images. I'm confused regarding 2 points -
They have a section "Endpoints", which gives the url for fetching images using tags - https://api.instagram.com/v1/tags/{tag-name}?access_token=ACCESS-TOKEN
At the same time, when i try to submit for review (under Permissions Review section), in order to get access token, i get this message -
"This use case is not supported. We do not approve the public_content permission for one-off projects such as displaying hashtag based content on your website. As alternative solution, you can show your own Instagram content, or find a company that offers this type of service (content discover, moderation, and display)."
The 2nd point makes me believe that Instagram has stopped sharing hashtag images to apis, at the same time i can find a lot of widgets still fetching hashtag images. How do they do that? Can anyone point me in the right direction?
The 2nd point makes me believe that Instagram has stopped sharing hashtag images to apis,
Correct. Instagram has made business decision to block most developers from accessing this content.
at the same time i can find a lot of widgets still fetching hashtag images.
This doesn't tell you much. They might have gotten their app approved for other purposes. Also it appears that Instagram has made some exceptions for big apps (like Tinder). Life is not fair.
How do they do that? Can anyone point me in the right direction?
You probably cannot. 99% of the use cases are not allowed and so they will reject your app if you try to submit it. Read this short article about what you can and cannot do with the new Instagram API
The other widgets you are talking about probably have presented Instagram with one of the valid use cases to fetch the data. They are able to get only the public content. This new restriction is probably a business decision. If you would still want to get the data you are looking for, you shopuld possibly go to a third party data provider who sell such data