So I have recently found out about Google Infographics QR Codes API which is very easy to use and I have yet to find a better alternative. Example: https://chart.googleapis.com/chart?cht=qr&chs=200x200&chl=Example:
However their documentation page (https://developers.google.com/chart/infographics/docs/qr_codes) says this: Warning: This API is deprecated. Please use the actively maintained Google Charts API instead. See our deprecation policy for details.
Also Google Infographics main page(https://developers.google.com/chart/infographics/) says the fallowing:
Deprecation notice
While the separate Google Charts service is actively maintained, the infographics service was deprecated in 2012 and turned off on March 18, 2019.
Go to Google Charts
About Google Infographics
This deprecated API serves static PNG images via URLs you can place in the src attribute of an tag.
As you can see eventhough Google says that it is turned off the API for QR Codes still works fine. Does this mean that I can still use this API with no worries? If not is there an equivalent API?
Using a deprecated anything is never a good idea. deprecation notices are there to tell developers that they need to move away from something because its due to be shut down.
If its deprecated that means they will turn it off. They start turning it off on "March 18, 2019". It can take a while for it to be completely turned off and some APIs continue to work for a year or so before they stop working all together.
I would not use this or develop with it as it is going to stop working soon.
Recommendations of equivalent APIs is out of scope for Stack overflow i suggest you Google it.
Related
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
So, I stepped once at this problem. I had offered a website that used the SoundCloud API. Everything worked properly. Content was extracted from the JSON and placed in the layout of the website. However, I received an email one day from the owner of the website, which indicated that the website did not work properly. I then came out to investigate and came to the conclusion that the "problem" was not on my side, but at SoundCloud's side. I studied on the API page of SoundCloud and came to the conclusion that the API had received a major update, making the link with SC and the site no longer worked.
Lately I'm trying many new APIs to, including those from Instagram and Dribbble. I was therefore wondering if it is at all possible to ensure that such problems can be reduced in the future or it might be appropriate API pages of this third-party APIs to monitor?
There's no "right" answer. After many years of using and maintaining many APIs here are some of the conclusions I've come to:
The best providers let you work with a specific version of their API whose interface and expected behavior never changes. They might release bug fixes and new endpoints, but you can be confident that as long as the API is supported it will not break your system.
A good provider will provide an end-of-life date for each version of their API. It's up to you to keep track of when you need to update.
Paid services will often be supported longer than free services. Plus the contract / SLA will guarantee it remains available for a specific amount of time.
The most popular APIs often have mailing lists and/or blogs. For those that offer it, sign up to be notified of updates. For those that don't you'll have to monitor their blogs or news posts. And I suggest not using any service that would drop support for an API version without warning.
Anyone having trouble building API's with the new Kimono Desktop app. When I click create API the browser just stays on create API screen loading but nothing happens.
I even tried building an API that is the same as one I built when Kimono was still in business and no luck.
My existing api's still run and pull data fine.
Working just fine here.
Just a shot in the blue...did you install the new extension specifically for the desktop app? The old one can't work anymore since Kimono disabled the online service.
You can't build new APIs I think - only existing ones. :( Said something like it was not the acquiring company's policy to provide this publiclu available service but since they did not know how many businesses depended on their APIs they decided to allow existing APis to run.
You can also use their software for replace the online API. But it's an abandonware.
It's working great but on some website I can create new API because of an error.
I just find a possible (free) product that can replace Kimono : Datascraping.co.
They will include an REST FULL API within few days / weeks, as they said here.
It's a good software, but comparing to Kimono Desktop it's a little much more complicated.
Kimono got bought out and it's not working anymore.
Import.io is good but it kinda expensive for me. I've tried the free trial before but see the price starts from $249, so... https://www.import.io/standard-plans/
I don't have any progamming skills so I know very little about some web scraping frameworks like Scrapy.
You may want to look at this new web scraping software called Octoparse.
In case you want to know, here is the link:http://www.octoparse.com/
It takes a little time to begin. But they have rich tutorials on the website. Plus it doesn't require programming skills.
They provide cloud-based scraping service and API access.
You can use it to create API but you have to pay for the service. Free version doesn't have the API and cloud service.
I've been using it for 2 month with the Standard plan $89, which a lot cheaper than import.io. So far so good.
Hope it would be helpful for you.
I'm new to Instagram API and my question is how to get complete access to Instagram's API without any limitations - like API's that any other Third-Party Client Apps Like (6tag /ink361.com/insta(X))uses .i want to give my users complete access so they can (like - repost - regram - Edit - ...).
and as I read in the official documentation there is a Sandbox / Live Permission/Condition that developers can get to have that kind of Access.
If I understood you correctly, you are trying to built an app similar to the core functionalities of Instagram (or most of it!).
As you have said, they have introduced Sandbox features post November 17th, so any app created after that date will be running in Sandbox mode until you give it for a review.
Few things to note here:
They are restructuring their APIs, meaning there are lot more restrictions and validations!
I'm not sure, but if you search on Google about their restructuring of APIs, it clearly states that Instagram is trying to block an app which has most of the core functionalities of it - likes/posts/feeds etc. This is to secure their users' data and prevent malicious activities.
Most of the endpoints are restricted and some of the old ones are slowly being deprecated.
So, I guess from now on you can't build an app on Instagram which is similar to theirs. Regarding the existing apps which does the same, they have to remove those deprecated endpoints as these new features will be imposed on them post 2016!
At the moment, you can the endpoints available to you are documented on http://instagram.com/developer/endpoints/.
Hope it answers all your queries!
I'm a student working on a project related to SEO; I need to write an optimization tool, so I'm writing an application using C# and Windows Forms. The main part of the application is for keyword selection, and I want to use the Google AdWords API to obtain a list of keywords.
I downloaded the C# client library, but can't understand how to set up the project: I am getting the error:
"An API exception has occurred. See ApiExecption and InnerException fields for more details".
Maybe I have made a mistake when I edited the App.config file as I haven't changed anything else. Can anyone advise me where I should begin? I would be grateful to hear your ideas.
Unfortunatley, the AdWords API isn't as open as you might think: It's meant for ad agencies managing large accounts, or software vendors who want to build ad management platforms. You need to apply to Google for an API key to gain access; they used to give them out to nearly anyone with an account, and it took about 14 days to process the application. However, Google has got very strict about their terms and conditions over the past 12 months, and to put it simply, you probably won't meet them if you're building an SEO tool; even if you apply to build a full platform, you'll need to wait six to ten weeks for approval as they've got a huge backlog of applications to process at the moment.
As this is just a student project, you should actually be able to get away with just using the AdWords API sandbox, which is open to anyone with a Google account. This won't give you real keywords or stats, but would demonstrate your understanding of the platform.
Another option would be to check out the Ad Intelligence Service of the adCenter API; you'd still need to open an adCenter account (with a $5 activation fee), but you should be able to get an adCenter API key without waiting too long. The stats available from Microsoft won't be as extensive as what Google has to offer, but will still be relevant to the at least the US market. Also, being Microsoft, they've got a good range of C# examples.
You could use the sandbox, but it is good only for testing purposes. You won't get real values for traffic estimation and keyword ideas.
To use the sandbox, what you need is a Google account (your gmail account for instance). To initialize the sandbox,
In your App.config, put email/password/developerToken as your email / your password / youremail++USD (e.g. john.doe#gmail.com++USD)
Run the GetCampaigns.cs code example. It is under v201109/BasicOperations folder in the C# examples project. This will initialize the sandbox.
Run the GetAccountHierarchy.cs code example. It is under v201109/AccountManagement folder. This will give you 5 client emails and their customer ids.
Use one of these customerIds in the ClientCustomerId field of App.config.
Run any other code example.
The video is a bit outdated, due to recent changes in AdWords API, I need to update it.
you can find a very good article series about adwords api there: Google Adwords API
it is not that hard to learn how to use it! I think the API itself is very good documented and there is a good suppo from google.