What is the difference between the “Google+ API” and the “Google+ API (Sign-in)”?
The Google+ API (Sign-In) seems to be suited at allowing a developer to integrate the Google login in into their application to allow their app to have an OAuth token to interact with Google services.
The Google+ API on the other hand is just the Google API that allows access to a users Google+ API data, you will need an authentication token to access this data.
The two different quota buckets refer to two different subsets of the API that are available. You can see https://developers.google.com/+/api/#quota for the details, but broadly speaking:
The Sign-In portion applies to methods that specifically need the plus.login scope. These include people.get, people.list, moments.insert, moments.remove and moments.list. This is a much larger quota to encourage people to use these methods.
The other, more broad, bucket is for all other methods, including those for Activities and Comments and a few others for People.
Related
I will like to know if its possible to retrieve a list of the most followed users (say top 20 users) on twitter through twitter's api. I cant see how to achieve that through any of the endpoints. How do web apps like this https://socialblade.com/twitter/ get that kind of data?
Any insights on this will be helpful.
There is no API for this. You would need to take an opinionated view of the high-volume celebrity accounts, and then watch the accounts by polling the user endpoints regularly. You could also use the commercial streaming APIs to watch the most Tweeted accounts and check the user objects on a regular basis.
(note that this is the same answer you were provided on the Twitter developer forums)
Google has a habit of providing multiple means to achieve a goal. And of ditching services when they feel like it. If I would need to implement a "sign-in with Google" authentication feature today, which one should I pick? Google Sign-In or
Google+ Sign-In? Or to put it differently: which one will survive the longest?
Use Google Sign-in. It's the second iteration of Google+ Sign-In so it's pretty similar but is simplier and faster to implement. Google Sign-In has gapi.auth2 and gapi.signin2 while Google+ Sign-In has gapi.auth and gapi.signin.
That being said authentication products generally have a deprecation period of a couple years so Google+ sign-in would be around for a long time even if it was deprecated today.
Sorry this question might seem a little dumb, but does instagram limit access to the access tokens they give you. I know on twitter you're limited to 100,000 access tokens, so does instagram do the same on their api? Lets say I have 150,000 users, will instagram's api allow those users to be authorized?
The official documentation does not say about any limits about access tokens. However they have limits per hour.
Global rate limits are applied inclusive of all API calls made by an app over the 1-hour sliding window, regardless of the particular endpoint. The limits are applied independently from each other; authenticated calls are not counted against the rate limit for unauthenticated calls and vice-versa.
So the answer is No, as of now.
I am trying to create a site where you can login with Google+, but I am having some problems understanding the Google+ API.
Can anyone explain to me how to fetch information, such as e-mail, name, id, etc. or give me a good link for a site where I can find some documentation about this.
Before you suggest me to this site I have already read it but not finding out how to fetch info.
Google+ Sign-In provides users the ability to authorize your application to retrieve data from the Google APIs based on the scopes that you set for your button. When a user authorizes your app, the sign-in callback returns you an OAuth 2.0 access token. This token gives you the ability to queries any of the APIs that your scope granted access to, this is not limited to Google+ APIs. You pass your access tokens to the API when you make requests.
Basically, you read the prereqs and didn't continue reading the API docs for the lower level details specific to the API that you are interested in. In this case, it sounds like you want to retrieve a person's profile (A "Person resource") by using the people.get method. At the bottom of that page are code examples for a variety of languages.
Can I use Adwords API developer token for multiple applications? In more detail, say if I have a website where I am using adwords API developer token, Can I use the same token for another application. Ofcourse both applications accessing the same account after all.
Thanks,
Murali.
You can use the AdWords API across different applications with just one API token, just make sure though that you are caching the authentication response and re-using those tokens otherwise you'll hit the throttle limit. (Incidentally, logging in is possibly the slowest part of their API, so caching the response will speed up your application considerably)
No doubt you can use same development token for your multiple applications which are accessing same account. If your applications will access different account then it needs to get different developer token.
For the reference, you can read http://goo.gl/zLBPF
Hope it will help you.
Murali,
You need just one developer token, whether your application(s) access same account or different accounts (whether linked under the same MCC hierarchy or not). As a matter of fact, AdWords API Terms and Conditions explicitly prohibits you from getting more than one developer token.
If you use a developer token to make calls, you will be charged for API cost to the account holding the developer token. This is another reason why you should treat your developer token as a password and should reset it immediately if you expose it to the public by say, posting it publicly on a forum.
I also wish to point out that the official AdWords API forum is http://groups.google.com/group/adwords-api, you can ask your questions there and someone will answer your questions in a day or two.
Cheers,
Anash
Yes, Adwords even has channels that you can create to separate your ad campaigns
Adword Docs - Campaigns