I am in the process of writing a Voice app for Google Home (using DialogFlow) and Amazon Alexa (AWS).
Both voice apps back onto a custom .net WebAPI that serves the answers.
We have written a series of integration tests that test both the Natural Language Processing (Deriving the Intent) and also the backend service. DialogFlow provide API access to their NLP making these integration tests pretty easy to set up.
I am in the process of porting the app to Alexa via AWS and want to perform the same set of integration tests against the AWS NLP but cannot see if this is possible. Most of the testing for Alexa seems to be centered around testing Lambda functions (which we are not using). Does anybody know if it is possible to interact directly with an Alexa skill restfully?
Yes, it is possible, but a little cumbersome.
Alexa Skill Management API (SMAPI) provides RESTful HTTP interfaces for programmatically performing Alexa skill management tasks, such as creating a new skill or updating an interaction model.
You'll need to create a Amazon app to use it and send requests adding Authorization header with all requests.
Docs for implementing this can be found here
Related
I want to release to production an integration using the whatsapp business cloud api, but the business's number has already an integration with amoCRM. Does anyone know if both tools can work together?
So, I am building a solution for web and mobile platforms which provides users with some screens from where the data from the Database is retrieved and inserted by some forms. One of the core features of the application is a chat-bot with supervised learning.
As per my understanding of the Lex API, it can share the current
websocket connection with other aws-services like API Gateway and Lambda.
Also, I have come to know that the human handoff is not provided out
of the box in Lex like DialogFlow API and Azure Bots.
Therefore, I am planning to share the same websocket opened by the Lex API for interacting with the user with the API Gateway ( as it supports websockets ) and thereby creating a human handover.
Please suggest whether there is a better approach to this problem's solution or I am on the right path ?
P.S. My Application stack is Nodejs and Angular based and following is my app's architecture.
how to use AWS RDS in flutter dart code?
I went through - this post
It says -
I work on the AWS SDK team. I am not aware of any plans to support Flutter at this point. I will take this to my team as a feature request and will post back
Should I do as suggested here?
Build your own service layer using HTTP, gRPC that talks to some backend service that provides access to a data store. You can do this with Express, Rails, CloudFunctions, etc.
You can either use dart code to do HTTP/gRPC, or use Platform channel to wrap dart code around native iOS and Android code of AWS official SDK.
On another note, I'm highly concerned when you connect directly from mobile (Flutter) to database (AWS RDS). Please be aware that anything on mobile app can be reversed engineer, and your database connection credential is not safe. It's recommended to have only backend proxy, or at least severless (such as AWS lambda function) connect directly to database (not mobile or web frontend). The only exception is with Firebase Realtime Database because it has seamless integration with Firebase Authentication
Now I am creating an iOS application. I also implemented some web services. My requirement is : "The user should be able to call a web service API by Sending a Text Message(SMS)". After a lot of research I found out that there a provider called Clickatell(http://www.clickatell.com/). But I don't know how can I configure it? Please help me in configuring this. Or Is there any other APIs or SMS gateways providing this service?
Disclaimer, I do developer evangelism part time at Nexmo.
Here are a few SMS APIs that I've used (I've not really used Clickatell, but I've gone through the signup process, and the following APIs seem a lot simpler to use):
Nexmo
Twilio
Tropo
All three APIs are straight forward REST/HTTP APIs.
You can call the API directly from your mobile application, however, you should consider if you really want to then compile your API credentials into your application. It may be better to host a kind pf proxy that your application uses - here's some example code used as a verification service, but it's essentially the same concept: https://github.com/Nexmo/Verify
I would suggest to take a look at Mogreet's new Developer Web Site
Very easy to use REST/HTTP APIs and very powerful. It supports sending SMS/MMS with awesome quality for all media types.
I have been working on a PHP project recently and I have created an API that will be consumed by mobile clients. I am using CodeIgniter as it provides a nice restful interface out of the box. I am unexperienced in PHP development and especially securing PHP web services. I was hoping to solicit some information about how I should go about implementing user authentication with my API. The information is not super sensitive but I do need clients to authenticate with the service.
Since my clients are mobile devices I'm uncertain how to go about implementing a membership provider model using CI since I won't have the luxury of a session (or do I?). Will my users merely send their credentials each time a request is made using SSL? Can someone provide me with some direction or documentation that might help?
Thanks!
Use Phil Sturgeon's Rest API. He's already built these things in.
http://philsturgeon.co.uk/blog/2009/06/REST-implementation-for-CodeIgniter