How do I make a call to discovery API from Watson assistant's dialog with reference to this page
Where do I set the endpoint?
Related
I'm creating a Xamarin project to test Azure Notification Hub, but I'm having trouble going through the steps in this article
Under the section "Create a Firebase project and enable Firebase Cloud Messaging"
Step 6 is obsolete as Google seems to have changed their model to obtain a Server Key, or the Server Key does not apply to FCM.
Can anyone shed a light on how to obtain an Api key for Azure Notification Hub?
expanding DrDave's comment
From https://console.firebase.google.com/project/--your_project_name--/settings/cloudmessaging
Click on the three-dots menu of the "Cloud Messaging API (Legacy) 🚫 Disabled" Heading
Follow the offered link to manage in google cloud console, and there press the button to enable the googlecloudmessaging API
Wait a few minutes
Go back to your Firebase console Cloud Messaging Tab, and refresh.
See that the Cloud Messaging API header has changed to "Cloud Messaging API (Legacy) ✅ Enabled" and that a Server Key is now shown.
If you go to the Build section, Authentication menu item, and then click the 'Get Started' button, then navigate back to the Project Settings/General tab, you should see the API key.
EDIT: This is not the proper key for the Azure Notification Hub. See my comment below for the correct key.
There currently does not seem to be a proper answer to this.
When using FCM, if you head to the Authentication page on the Firebase Console for your app and select 'Get Started', follow the steps and then head back to the 'General' tab in your project settings page, you will see that it now has a Web API key.
This isn't useful for Azure Notification Hubs as if you try insert this key into the API key entry for a hub, it will not accept it.
The only answer seems to be to use the legacy GCM API, which is not ideal as it has been deprecated and certain APIs are no longer available.
I'm new to the concept of Docusign but I have successfully developed API for Envelope creation and View Url. For creating Docusign connect, I have created a Connect Configuration in the Docusign Developer Admin account. It would be a help if someone guides me on how to proceed with the Webhook Writer and Listener for the Envelope events in .Net core.I have my Event Notification object configured as well.
The other Questions mentioned related to Webhooks in StackOverflow are partial.
Welcome to our platform.
The first thing you want to do is to deploy your listener in cloud provider of your choice. We provide samples for Azure, GCP and AWS.
https://github.com/docusign/connect-node-listener-azure
https://github.com/docusign/connect-node-listener-aws
https://github.com/docusign/connect-node-listener-gcloud
Then for your worker, you want to look at the following code sample:
https://github.com/docusign/connect-csharp-worker-aws
or use related cloud provider. You will then need to update your Connect configuration with your listener endpoint.
In a nutshell, the listener will receive the events from DS Connect and queues them. The worker will pull the new events off the queue and processes them.
We have a couple videos and material coming shortly that will cover this topic in full details, so stay tuned.
I want to expose the REST API in WSO2 API Manager with the back-end service (XML over http). I wanted to convert the JSON request to XML and call my back-end service.
Please let me know how to achieve this in WSO2 API Manager 3.0
Use the json-to-xml-in-message mediation sequence.
Login to api publisher.
Open the api and go to the Runtime Configurations tab from the left menu.
In the Request section, click on Edit button of the Message Mediation option.
Select the json-to-xml-in-message mediation sequence from the Common Policies.
Click on Select and Save the api.
I am testing out this android chat application using Bluemix https://github.com/IBM-Bluemix/chatbot-watson-android
At some point in the conversation I will need to call a REST API/webservice to retrieve info about data that has been gathered and send it back to the user as a chat.
I don't want to do it from within the android application as the application wont work when I deploy it to another platform (e.g. slack).
Is there a way to call REST APIs from within watson?
I don't think the conversation service can do it directly, but can it link to another Bluemix service and use the result of that?
If you are already using some form of middleware this can be achieved by setting an action tag in the .JSON editor of the node that should fire the action. This then gets picked up by your middleware listener.
Alternatively try the new cloud actions feature that has just been released here https://console.bluemix.net/docs/services/conversation/dialog-actions.html#dialog-actions which is really simple and easy
I would create a server to intermediate the communication between your app (android) and the conversation service. This server could call/retrieve the required data before sending the conversation response to your app.
As you're using Bluemix, you could use Node-Red to easily do this.
Here is an example of an app that I made exactly this.
If you are starting with Watson and Bluemix, I strongly advice trying to use the Node-red starting pack. It's really easy to integrate Watson services and call REST API/web-services, even integrate with a database.
Here is a starting point to this:
https://nodered.org/docs/platforms/bluemix
Happy coding!
I am using WSO2 API Manager to expose few APIs. But I don't want that the consumer use the API store for the subscriptions. The creation of subscriptions/applications and Access tokens should be managed through by my custom web application.
I have checked the WSO2 API Manager docs https://docs.wso2.com/display/AM210/apidocs/store/ and imported the swagger in SoapUI. When I try to invoke the store api of my local API Manager I am getting the HTML content of API store page. see below screenshot.
Can anyone please help what I am doing wrong? Or is there any other way to the requirement.
You need to pass token which is generated by passing scope and client secret key and password as described in https://docs.wso2.com/display/AM210/apidocs/store/#guide