I'm having a difficult time to use Google Places API autocomplete with a API key. In my production site, we are using it without a key, works perfectly until traffic reach the request limit. After some research, found out I will get higher request limit using a API key. However, after I added the key (even no restrictions), the address field in my form is disabled and showing "Oops! Something went wrong.".
Here is Google API URL I am using
https://maps.googleapis.com/maps/api/js?key=[my_api_key]&libraries=places&callback=initAutocomplete
I was thinking it must be something wrong with my code. Then I use Google's official autocomplete sample code with my API key and no further modification, same result. Using it without a key always work.
I confused. I don't believe the code is wrong. Anyone can give me a hint?
Found the problem. I enabled "Google Places API Web Service" in Google Developer. However, this is not enough. I have to enable "Google Maps JavaScript API" as well.
Thanks the reference to Google Maps API error: Google Maps API error: ApiNotActivatedMapError
In your Google API Manager -> Credentials, did you setup
You can also check your console, Google will tell you why "something went wrong".
Related
)
I have made an app,
i made a free app, which shows a list with restaurants. To see which restaurants are in your near i implemented the google map api v3.
On the map are icons which show the restaurants.
When i submitted the app on iTunes, i got the question: Does your product contain encryption?
I have looking for information on the google site about encryption, but i haven't found any information.
I don't know if they use encryption and i don't know which encryption they use.
i read on this site, but i don't know if my app/the google map api v3 is is described by note 4 and free from encryption control.
Has someone experience or information?
Do i need a ERN-Certificate or something else?
Thanks in advance
It's more to do with whether your application performs any actual encryption in the source code.
See this post - Does HTTPS in my app considered "Encryption"
I'm trying to use Google's Webmaster Tools API to download a CSV file of recent search queries.
I know how to do that using their Python example at http://googlewebmastercentral.blogspot.com/2011/12/download-search-queries-data-using.html
But I want to use OAUTH2.
Here's the problem: The download url for CSV downloads is:
/webmasters/tools/downloads-list?hl=%s&siteUrl=%s
But the Google data API only lets me use OAUTH2 against:
/webmasters/tools/feeds/sites/
So the token I get when I authenticate doesn't provide access.
It SEEMS insane that they'd have some of their data available via OAUTH2 and some of it only using username/password.
Does anyone know a request URI I can use to download the query report via OAUTH2? Or is this API as nuts as it seems?
My $.02 would be "yes, it IS as nuts as it seems."
If you look at the Google APIs Console (https://code.google.com/apis/console) the Webmaster Tools API is conspicuously absent.
I attempted to go down the same road & use OATH2 for the GWT API & was not able to make it work. Using the 'basic authentication' was the only solution.
edit April 2015: basic authentication has been withdrawn by Google and no longer works
I just ran into this, I am shure it has to be possible with OAuth2, corresponding to this sentence:
Activate the Google Site Verification API in the Services pane of the Google APIs Console. (If it isn't listed in the Console, then skip this step.)
https://developers.google.com/site-verification/v1/getting_started
I'm implementing server-side interactions with YouTube and I'm a bit lost with the kind of Product/App you need to create in order to publish videos via the API for example.
Looking at the OAuth2 doc, it says that I need to register my app with the API Console (looks good so far, very similar to creating a Facebook App).
But then, I looked at the Google .NET library and here it says that a Product needs to be registered in the YouTube dashboard... Not sure to understand how these are complementary. If anyone has a synthetic explanation (which I didn't found in the docs), I would be grateful.
Thanks
I'm not 100% sure but I believe:
The YouTube Dashboard was originally setup prior to the announcement of YouTube API v3, which is yet to be released. You use the Dashboard to register your application and get a YT Dev Key. You can also use the Dashboard for some extremely low level application statistics.
The API Console is Google's attempt to form one administrative console for ALL of their APIs. Since Google is transistioning to oAuth 2 authorization, you will need to use the API console as well in order to apply for a clientID, redirectURI, and clientSecret if you want to authorize with oAuth 2.
At this time, if you do not want to use oAuth2 you do not need access to the API Console. However, know that in February of next year YouTube is going to kill all other forms of authorization (sub, clientLogin, oAuth1).
So to try and simplify things:
Use the API Console to get your oAuth2 in order
Use the YT Dashboard to get a YT Dev Key
In the future, when Google goes lives with YouTube API v3, you will probably want to switch to a new Dev Key from the API Console and leave the Dashboard all together.
I'm working on a Google Drive interface for Emacs. The concept is that Emacs could provide a platform-agnostic way to load, modify and save text documents stored in Google Drive. I've registered my app and can authenticate with OAuth2 and get a file listing with the Docs List API, but when I try to execute an Insert with the Google Drive API, I see an error:
"The authenticated user has not installed the app with client id ..."
Reading further, it seems I need to publish my Emacs application in the Chrome Web Store to get access to the Drive API. That doesn't make sense to me...I noticed that there is a FUSE project in development for Google Drive, which suggests that native development is possible. When I skimmed the code, however, I didn't see a Chrome Web Store component to getting it working.
Am I trying to misuse the API, or is there an route to make this work that makes more sense?
EDIT:
According to Ali Afshar, of the Google Drive team, installation is no longer required to use this API. So what follows may no longer be relevant, but will be left for historical purposes.
So, first off the API does not support application development in the sense that we are both doing it, I wouldn't use the word native though. The good news is I have been doing some research and Google Drive is really just a rebranding of Google Docs. So the Google Docs API could be a good choice as well for the same purposes.
Anyway, here's the steps to solve the error: "The authenticated user has not installed the app with client id ..." Which is a 403 error, for the sake of this answer. These steps assume you have set up an app in the chrome web store as is required, and installed it. I am working on my local machine too, with my project: http://github.com/tom-dignan/gdrive-cli which I have gotten past this error, so I think you should keep plugging away at your emacs version, because I think we can make this work.
a. Open the Google APIs console.
b. Confirm you've already enabled the apis under "API Access" both the API and SDK for Google drive should be enabled. There you get your client secrets/api keys and such. I am almost positive you've done this already, so go ahead to C. (this is here for others who may have missed it)
c. In the left navigation bar, under "Drive SDK" you will need to do the following:
Add a "Support URL" (required)
Add at least a small 16x16 application icon (required)
Add "OAuth Client ID (Required)" under Drive Integration (I was just tinkering and this seems to be the key field.)
Add "Open URL (Required) URL to open for your app from the google drive UI."
Check off "Multiple File Support"
Add some MIME types and file extensions, "text/plain", and txt for example
Add the the auth scopes:
https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/userinfo.profile
Don't bother trying to add the auth scopes for Google Docs here, because it won't work. Google does not want us to use it that way because files that drive apps create should be private to that app. Integration with Google Docs will have to be separate.
Now I know you must be thinking "why do I have to add some of these..." It's because the form makes them required fields. In mine, I put a couple URLs that point to static HTML pages.
Once you've done the above, clean up your state and reinstall your chrome app. Then try your code again, and it should stop giving you a 403.
I see everywhere that google plus api is readonly. But i saw this app screenshot.
How did they do then? Even the docs say its read only.
The API is indeed still read-only. We worked directly with SXSW on this year's mobile app to enable sharing... it's not a feature that is generally available at this time.
The note at the top of the REST API documentation page seems to answer both questions at once:
Note: The Google+ API currently provides read-only access to public
data. All API calls require either an OAuth 2.0 token or an API key.