You have exceeded the quota or rate of requests allowed for your resource. Make sure your resource key or token is valid and in the correct region. A common reason is a header that's too long. Or, the value passed to either a required or optional parameter is invalid. HTTP status codeĪ required parameter is missing, empty, or null. The HTTP status code for each response indicates success or common errors. "LocaleName": "Chinese (Mandarin, Simplified)", "Name": "Microsoft Server Speech Text to Speech Voice (zh-CN, YunxiNeural)", "Name": "Microsoft Server Speech Text to Speech Voice (ga-IE, OrlaNeural)", "ShortName": "en-US-JennyMultilingualNeural", "Name": "Microsoft Server Speech Text to Speech Voice (en-US, JennyMultilingualNeural)", "Name": "Microsoft Server Speech Text to Speech Voice (en-US, JennyNeural)", This JSON example shows partial results to illustrate the structure of a response: [ The WordsPerMinute property for each voice can be used to estimate the length of the output speech. You should receive a response with a JSON body that includes all supported locales, voices, gender, styles, and other details. header 'Ocp-Apim-Subscription-Key: YOUR_RESOURCE_KEY' Here's an example curl command: curl -location -request GET '' \ Ocp-Apim-Subscription-Key: YOUR_RESOURCE_KEY This request requires only an authorization header: GET /cognitiveservices/voices/list HTTP/1.1 For more information, see Authentication.Įither this header or Ocp-Apim-Subscription-Key is required.Ī body isn't required for GET requests to this endpoint. This table lists required and optional headers for text to speech requests: HeaderĮither this header or Authorization is required.Īn authorization token preceded by the word Bearer. In next article, we will go through the Creation of the App.Voices and styles in preview are only available in three service regions: East US, West Europe, and Southeast Asia. You can download the swagger definition of the custom API for reference. Now we have the custom API to the Bot service ready and we can use it to build our App. You should see a response from the QnAMaker service. Navigate to the Test tab and under Operations enter a query string. Go back to Manage custom connectors and click Edit on the connector you created earlier. In the pop-up enter the subscription key information. In the Test tab, click on New Connection to create an instance of the connection. Once the connector has been created, choose the Test tab. You should now see answer and score added to the Body output.Ĭlick on Create Connector. Paste the response from the Postman query as below into the Body field. Edit the Content-Type in the Request header and marked the Is Required as No.Įdit the Response section by clicking the default. This was already added in the previous step. In the Definition tab, edit the General Section to update the Summary, Description and OperationID if required.Įdit the Request section and remove Ocp-Apim-Subscription-Key if it exists. Enter Ocp-Apim-Subscription-Key as the parameter and label name. In the Security tab, choose authentication as API Key. In the General tab, under Custom connectors choose to upload the Postman collection saved earlier.Įdit the name of the Connector at the top of the page, upload an icon for the connector and click Continue. Refer to the PowerApps documentation or the Postman documentation to for the detailed steps.įrom the PowerApps portal, choose Data and custom connections. Save the result in a collection and export the content as a json file. Let’s create a custom connector the Bot service.įirst, test the connection to the Bot service using Postman. PowerApps provides an easy way to create a custom API to any RESTful service using a UI wizard in the PowerApps portal. We’ve so far created the BoT Service at Build the Bot service – QnA Maker Welcome to the second blog in our blog post series on Creating smart Apps with PowerApps and Microsoft Q
0 Comments
Leave a Reply. |