Please forgive me, I am fairly new to the Dialogflow Api (v2.)
I am starting off with testing these API calls using the Google API Explorer utility on the right side of the page.
My question is specifically about the "access_token" field:
Is this supposed to be the JSON authentication file that I downloaded from the Google Cloud Console when I created a new service account?
If not, then where do I find the specific resource I am actually supposed to pass into this field?
Side note: I read in the support section: "Google engineers monitor and answer questions about the Google API Explorer on Stack Overflow using the tag google-apis-explorer." Thank you all in advance for your service/help in this topic!
The access_token field is a higher-level field used across the API by some tooling. In some manual client libraries, you might need to use it, but for the API Explorer utility and for most use-cases, you can ignore it. This is true of most (maybe all) fields under the "Show standard parameters" zippy.
The documentation on the left side should explain the relevant fields you need to fill in to successfully complete a request. Keep in mind that even some of these fields are optional; you can leave them blank if they are not relevant to your goal.
Related
I want to be able to pull all text messages from a google chat space.
I'm looking at the spaces.messages.getbut it assumes you have the ID of a message. In similar programs (MS Teams), you can call an endpoint to list all message ID and then call the message API to extract the contents of an ID. However, google chat has no such API.
Has anyone come across a way to do this?
This is currently not possible
There is already a respective feature request on Google Issue's Tracker.
I recomment you to star it to increase visibility and hope that it will be implemented soon.
I am a beginner trying out api for fun.
The problem is, lets say, I want to write a simple windows program with golang to let my friends read and edit one of the sheets saved on my google drive. How can I do this without having them download a credential file?
What I want it to do is simply redirect them to the Oauth Page right away, and if their email address is one recognized by the app it will grant them access to that google sheet.
What i think you need is to integrate your go app with Oauth protocol.
More specifically, with the Google provider.
This is mainly 3 steps:
add the oauth client to your application
something like this: https://github.com/golang/oauth2
See their docs on how to do it.
go to google dev documentation and see how to integrate google auth flow into the client: https://developers.google.com/identity/protocols/OAuth2
I'm not sure if google has something more specific for google drive integration and/or go-lang client in particular. Please do some searching.
make the glue code on your go app so that the user can interact with this (the login button (or command, if it is terminal based), error messages, logout, etc)
More questions will appear when you start to do this, however it is a great example to learn Oauth as well.
General guidelines:
https all the queries or oauth is basically useless
oatuh has many auth-flows and you must choose which one(s) you support. use whatever google documentation recommends for m2m scenario (machine 2 machine)
log errors so that your friends can send you a log file for you to debug issues
maybe set some feature flag so that you can simply disable this feature to run/test localhost ? maybe useful? you decide.
When searching in Yammer it uses an /api/v2/search endpoint like this:
https://www.yammer.com/api/v2/search/models?search=test&start=0&size=20&model_types=threads&_network=xxxxxxx&relevance=DEFAULT
Compared to the v1 search endpoint this returns more data. We need this data. And we successfully tested using this v2 endpoint.
Now the question: Is this v2 search endpoint safe to use? Is it "official"? Maybe somebody from Yammer reads along - on their Help page it says:
We encourage you to post all programming questions to StackOverflow
with a #yammer hashtag
So here we are. Any help is appreciated.
The Yammer v2 search API endpoint is not yet officially supported for third-party use. This is because we anticipate the need to make changes to it as we build it out. There are no plans to lock developers out of experimenting with the v2 search API. However, when developing any important functionality against this API, automated testing should be used to detect any unannounced breaking changes that we make while we continue to build it out.
Currently, I have been tasked to utilize the Google People API to ask for a user's basic Google information along with their public phone numbers. So far the results have been positive.
The solution my team and I have incorporated the Google People API integration in has the capacity to be utilized across thousands of domains. As a result, my question is simply, How can my team members and I ensure that any our clients that utilize our solution with their own particular domain get our new functionality built with the Google People API?
Keep in mind, our clients have the flexibility to have http/https and any subdomain on their site. Entering each domain possibility for our client base one by one would not be an easy task. I'm seriously hoping there is a solution around the single, explicit origin entries.
Thank you for your time and help.
Warning:
You must remember that if this is source code you are giving your clients that you are not allowed to release your client id and client secret. This includes plugins and scripts.
On November 5th 2014 Google made some changes to the APIs terms of Service.
Asking developers to make reasonable efforts to keep their private
keys private and not embed them in open source projects.
So if your clients could view the code of your application and see your client id and secret you should not be giving it to them.
Read more about this issue Can I really not ship open source with Client ID?
Recommendation:
The best solution for you will be to instruct your users now to create there own project on Google Developer Console and create their own JS origins.
You may just have to provide your own wrapper around the target API where you authorize the client request yourself and then do the request from Google using your own credentials.
I am somewhat new to code, and even more so to the Google Apps API. In the organization I work with, I have so far managed to write a couple of console apps that we run to apply signatures, and manage mailbox delegates as needed.
In regards to the Email Settings API, specifically the signatures portion, is there a way to check this box:
"Insert this signature before quoted text in replies and remove the "--" line that precedes it."
via the Email Settings API? I've looked through the API documentation, and even the .NET api reference docs, with no avail. Any advice will be helpful.
This feature was available while it was a lab (through the admin console, not API), but not anymore now that it has 'graduated'.
It has now been submitted as an official feature request. Hopefully more people request it.
I was told that setting the footer through the API does show up before quoted text, so if that is true, and all you need is a footer for everyone in organization, you might be in luck.