Since September 5th, 2018 the custom search API dashboard screens no longer works.
I get no stats, no quotas for the project that I use. The service is still running from the front end, signing in with a personal account, other then the existing one I use, I find there is a new metrics section that has been added but that is not available to the other account? The only work around is to into billing -> reports -> SKU for the current day to figure out what the quota usage is. Is this a bug, or is there somewhere to upgrade the existing dashboard, new way to use the custom search, anyone else having this issue?
This is now fixed, google fixed the dashboard. As of Sunday the 9th, they didn't move anything it was busted, and they added there restricted service monitoring to the quota section. Was not aware Google developers would leave something that long as an issue, hence why I thought it was my issue. Still would have loved to have know where to go to see current list of issues.
Related
We are using People API to fetch details from Directory . The API is not returning the name for most of the people in the directory. 2 accounts in our GSuite account alone provide the name field, while the others don't. However, other details like emailAddresses and phoneNumbers are available for everyone.
We didn't find any finer grained control for individual fields when using the setting External Directory Sharing → Domain and public data
We tried to change the setting from default to External Directory Sharing → Public data and authenticated user basic profile fields. However, this results in API response showing PERMISSION_DENIED error.
For one of the users in directory, we created Google Currents account. When the account was created and active, the name field became available for this user. After the account was deleted/deactivated, the name field was no longer available.
People API being used:
GET https://people.googleapis.com/v1/people:searchDirectoryPeople?query=a&sources=DIRECTORY_SOURCE_TYPE_DOMAIN_CONTACT&sources=DIRECTORY_SOURCE_TYPE_DOMAIN_PROFILE&readMask=emailAddresses,names,phoneNumbers,photos
The docs we have referred to so far are as follows:
People API - Search Directory:
https://developers.google.com/people/api/rest/v1/people/searchDirectoryPeople
Let third-party apps access Directory data:
https://support.google.com/a/answer/6343701
A merged view of people information:
https://developers.google.com/people/#a_merged_view_of_people_information
Edit:
cURL command:
curl --location --request GET 'https://people.googleapis.com/v1/people:searchDirectoryPeople?query=s&sources=DIRECTORY_SOURCE_TYPE_DOMAIN_CONTACT&sources=DIRECTORY_SOURCE_TYPE_DOMAIN_PROFILE&readMask=emailAddresses,names,phoneNumbers,photos' \
--header 'Authorization: Bearer <access-token>'
This is a known bug with the People API.
You can find it here in Google's issue tracker: https://issuetracker.google.com/issues/196235775?pli=1. If this bug is impacting you, I highly suggest you leave a comment letting the team know you're currently facing the issue and leave a +1 by clicking the "+1" button on the top right.
In the comment section of this question, it was suggested that this behavior is to be expected and is related to privacy. It's safe to say that's not the case as 1. the issue was accepted as a bug by the Google team, and 2. all other information is successfully returned from the API aside from this field.
Additional information on the resolution
Back in August of 2022, the Google team explained the fix was being held up by a bigger effort:
Hello there - apologize for the delay, we did identify the root cause,
however the fix is blocked on another bigger effort. We recently
started making progress on the blocking issue, and will provide an ETA
as soon as we figure out some of the unknowns for the solution.
However, recently (January 17th, 2023), the bug was assigned to someone at Google. This may suggest that the bigger effort was completed and that the team is now unblocked.
Potential workaround
Hopefully the bug is fixed soon. But in case we're waiting for a while, these workarounds may help.
Email is reliably returned for all directory users. The OP doesn't mention the exact context in which he or she is using the API, but for some applications you might be able to get away with using email (e.g. if you're just trying to identify the Directory user to the end user).
Additionally, if user email addresses in your directory follow a uniform formatting, you should be able to parse those to get the name. This is the workaround I'm currently using. E.g.
john.smith#example.com -> John Smith
jsmith#example.com -> J. Smith
jsmith3#example.com -> J. Smith (if you're at a large organization, you may have to remove some numbers)
Meta Sidenote
Yes, it's valid to post that something is a known bug as an answer. Check out this link if you have questions: https://meta.stackoverflow.com/a/369622/1101602.
I am many errors on my Maps API Console.
I am the website owner, not the developer or webmaster.
Got an email from Google about new pricing. Below is the email.
Today we are announcing important changes, including our new name - Google Maps Platform, a simplified product structure, pay as you go pricing for all, and more. Please take a few minutes to review the announcement to familiarize yourself with the upcoming changes.
We would like to highlight a few updates that may impact your implementation. Beginning June 11th, we are launching our new pricing plan and providing all users access to support. We’ll continue to offer a free tier — all developers will receive $200 of free monthly usage of our core products.
How does this affect your current account(s)?
Based on your usage over the last 3 months and our new pricing plan, we estimate that your monthly cost will exceed the current $200 free tier.
I am trying to figure out why I have so many API calls.
I am seeing in the console, that in the "Google Places API Web Service" I have alot of "Zagat content in the Places API" calls, and they all result in error.
I am trying to figure out how this is happening, but not finding any info online. I see that the "zagatselected" parameter was discarded May of 2017. I can not figure out what is causing these errors.
Everything has been working fine, I have my own API key, and have for a long while. The only reason I am really looking into this, is because Google will now start charging me monthly.
Is it possible you expose your Maps API key to the client, don't have any restrictions on it, and someone else is calling the API/raising those errors?
If you have a snippet of code like this....
<script src="https://maps.googleapis.com/maps/api/js?key=[APIKEYHERE]&libraries=geometry,places&callback=initialize">
...on a public web page, it would be easy for someone else to take the API key and use it themselves, unless you add a IP or referrer restriction to only allow it to be used client-side from your website. You can set up restrictions on who can use your API key following these instructions.
I suspect that the new Google Maps and Places API pricing scheme (which significantly lowers the number of free Places API calls) might cause some less ethical users to use keys they can scrape off websites.
With Places API, it provides the ability to add new places. How much are we sure that Google does not use these custom added places for their own marketing and research purposes. What if you want to keep these new places private to your applications. The Add Place section does not talk anything about this.
Does anybody have any information around Google privacy policy around adding new places?
As per the documentation:
By adding a place, you can supplement the data in the Google Maps
database with data from your application. This allows you to:
Instantly update the data in Google's database for your users.
Submit
new places to a moderation queue for addition to the Google places
database.
This means that places added via the Places API are reviewed and, if approved, added to the global places database that is accessible for all users. They will not be kept private to your application.
UPDATE
The Place Add has been deprecated on June 30, 2017 and will stop working on June 30, 2018. So you cannot use this method anymore. For further details please refer to the corresponding geo blog post.
I am using the Google Translate API (for REST). There is a quota of 2M characters/day. I would like to increase that - how do I do so?
I have followed the instructions provided to no avail.
Google Developers Console
Select Project, Expand API & Auth, Click the Translate API, Go To
Quota
I have clicked the 'Apply for higher quota' which returns a 'page
not found' error
I have clicked each 'Change' button and input a higher number.
When Submitted it sits there; there is no response.
I have also gone to the API Console, and selected Quotas under my Project. There is no link to 'Request more...' for the Translate API, as there is with other APIs.
This is a bug. It also appears in the documentation. https://cloud.google.com/translate/v2/pricing. Google has been informed they are in the process of tracking someone down to fix the issue with the file at this time.
How To increase quota from the Console
You can / or should be able to extend it from the console.
Go APIs-> click on Translation API -> look for Quota click on that
You should be able to click on Apply for Higher quota. But the link isn't working right now. Google is on it. I will update this when i hear from them that it has been fixed.
Again Well spotted, and thank you for pointing it out :)
Update: I was told by Google that you should be able to increase your quota by enabling billing. There is also a thread about this on Google's Forums
Change quota fails; Apply for higher quota URL is broken
Update 2 (direct from Google)
Fixes were pushed on February 27th, they include:
Telling the user on the Quota tab that they have to enable billing
Removing the option to change the quota when billing isn't enabled
We no longer show a red warning triangle that 0% of 0 quota has been used
What we haven't fixed is the link to the document on how to apply for a quota
increase, the bug for this has been bouncing backwards and forwards
but we seem to be closing in on a resolution.
After creating both a Chrome Web Store listing as well as a duplicate listing tuned for the Google Apps Marketplace, I have filled out the Marketplace Listing Review Request. I've had to edit the second listing several times as I've uncovered issues like not including the app member in the manifest, and I have no idea of the overall status of the request. Is there a way to find out?
My big concern is that something is still not right or that I might have missed a step or done something else wrong in the process of submitting the listing. Since there's no obvious validation around the Marketplace Listing Review request, I'm not 100% sure if I'm doing it perfectly. This is my first listing. Help?
First step would be to provide your Chrome Web Store Item ID as jonathanberi mentioned. Once you do that I can take a look at the application for you.
The reality is that we don't check and test new GAM applications every single day. It's more accurate to say that your application will be checked within 1-2 weeks from publication. If there are any issues, I or someone else on the curation team, will reach out to you to let you know of the problem and it's severity. Most of the time the issues aren't serious enough to warrant immediate removal from the Google Apps Marketplace and simply need to be fixed within a 30 day time frame.
So, long story short, no news is good news for GAM publications. If you don't hear anything from us within 2-3 weeks of your publication date, you can safely assume that your application has met all of our listing requirements.
I had the same problems and spoke to some very helpful folks at Google. Here is a summary of what they said:
Time taken to hear back: For new submissions their SLA for reviewing is 8 business days, but they usually do better than that.
Time taken for your app to show up on Google Apps Marketplace: 12-24 hours. When they approve an item it is automatically send to the public store, however it takes time to be shown in the Google Apps Marketplace search results due to cache propagation as time is taken for their robots to find it, index it and get it ready. (as of Jan 2017)