google actions account linking custom response - actions-on-google

When linking to a google account inside a google actions, the code to use in actions sdk (as per documentation) is:
conv.ask(new SignIn('To get your account details'));
What the system seems to do is, prefix the above text to a standard text. The response for the above code seems to be:
To get your account details, you'll need ... profile picture?
Is there a way to customise the rest of the response body? Thanks

No, there's no way to customize the entire message. While you can provide a preamble, the rest is standardized for consistency.

Related

Twilio SendGrid Global Email Statistics Access Forbidden

I have setup a SendGrid API key with full access and was trying to get global email statistics using the online tool that goes with the documentation ... but the response I get says access forbidden. I'm not sure what to do because my API key has full access. Can anyone with experience using the Twilio SendGrid API offer advice?
Twilio developer evangelist here.
I think the issue here is that you have the default on-behalf-of text still in the form. It's not a regular placeholder text, but actual text.
Delete the text that start "The subuser's username..." and try again. It should work.

Dynamically create skills for Actions on Google via an exposed API?

Is there an API exposed for Actions on Google, similar to what Dialogflow offers with their API? The only API-like flow I have found through my research is this webhook flow API, but that only deals with conversation requests, prompts, and responses, which I have already handled.
Ideally I'd like to be able to dynamically create "agents" and their conversation flows without having to use the AoG console, similar to what Amazon offers with Alexa SMAPI.
There's not a full API to do everything that you want end-to-end. Some parts, like Dialogflow and fulfillment, can be automated, but it will still require some manual work in the Actions Console.
I had a conversation with another developer on this subject once. As a workaround, which is admittedly hacky, they decided to use the Puppeteer library to programmatically control a browser instance to fill in fields and click buttons.
That may not necessarily work when the console changes, and isn't a good substitute for an API, but it may work for you.
Yes you can do it using Google Dialogflow REST API
Here are APIs for the agent :
There are many more APIs available for different operations.

Docusign REST API flow for signing pdf

I have an app that creates a pdf that the user has to sign online. I want to somehow upload the document and receive it back, signed by the customer, by "hand".
I tried to follow the quickstart guide, but it does not allow to sign documents (template fields are greyed out), and they are not created dynamically, so I canĀ“t use that approach.
What is the best workflow for achieving this? I mean, what APIs would I need to call and in what order? Has anyone gone through this process before?
Could you elaborate on what you mean by "hand"?
If you mean they need to print the document, sign it and then upload it then there's a similar question here Allow user to only Print and Sign for an envelope. The feature itself is called Print & Sign
REST API Reference: https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeRecipients/create#EnvelopeRecipients
Have a look at signer > requireSignOnPaper definition on that page.

ESPN Api Integration issue

I am implementing espn api, but having some issue, most api gives me this response.
{"timestamp" :"2013-02-25T11:19:02Z","message" :"This action is forbidden for the requested resource at your permission level. Please review the documentation for account level access.","status" :"error","code" :403}
I am using this api Espn MLB Standing
I want to know that where to review the documentation, i is there any need to purchase some api or anything else?
[EDIT]
One more thing there is ?apikey=:yourkey , so this key is same for all user or we have to get this according to user login.
I think you are using the wrong apikey or there is some issue in your URL query.
Your app will have a unique apikey. This key is same for all users who are using the app.
You should get a apikey by registering to their site and use it for development purpose.
My rep doesn't allowing commenting, but I thought I'd add the following here:
A small amount of ESPN API data is free, but much requires payment.
You probably don't want to publicly share your personal API key for security reasons.
Go to http://developer.espn.com/io-docs and plug in your API key and use the GUI to generate an API call/response. It's a good way to see a valid, working syntax that you can then drop into your app and edit as necessary.

Foursquare userless search iOS

is there a way to fetch the venues search in iOS without the user entering his password or showing some foursquare oauth website?
I don't think that this oAuth makes any sense for this kind of request, it should be just an REST api like so "https://api.foursquare.com/v2/venues/search?ll=-27.58818,-48.523248&client_id=JN00ABQBOCK5V54FQ1TWQFLOOIDU12UAZXURHXGXNK0ESJBY&client_secret=14ES1NXTCL1XC5HSLBUT4LWE4ROEDGNYKKWGGERZQGUKQ5JC"
but this one is deprecated =/
Any thoughts?
It's not deprecated, you're just missing the "versioning" parameter that specifies what version of the API you're trying to use.
Requesting https://api.foursquare.com/v2/venues/search?ll=-27.58818,-48.523248&client_id=JN00ABQBOCK5V54FQ1TWQFLOOIDU12UAZXURHXGXNK0ESJBY&client_secret=14ES1NXTCL1XC5HSLBUT4LWE4ROEDGNYKKWGGERZQGUKQ5JC&v=20111107 will remove the warning you saw in your response
Add a query string parameter to your request as follows..
&v=20111119 // Choose a proper version.
Update: this is actually a date. So make sure you send current date in yyyymmdd format against v parameter.
According to FourSquare's docs page on venue searching an acting user is no longer necessary:
Some endpoints (e.g. venue search) allow you to not act as any
particular user. We will return unpersonalized data suitable for
generic use, and the performance should be slightly better. In these
cases, pass your client ID as client_id and your client secret as
client_secret. Although the draft 11 of the OAuth2 spec provides a
mechanism for consumers to act via token entitled Client Credentials,
we do not currently support this.