I was trying to get API Key for AwesomeTTS (Anki)
I want to use Azure Text-to-Speech service REST API
I followed two YouTube videos (one is below and I can't find the other one right now)
https://www.youtube.com/watch?v=EcZF73bsme0
I only got an audio file, but I have no idea where is the API Key I need for ANKI.
I also read this article on Microsoft website many times
https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-text-to-speech#authentication
Could anyone tell me where/how I could get the API Key?
Thanks
Could anyone tell me where/how I could get the API Key?
You can get the API key by following steps:
Create an account on https://portal.azure.com
Create a Subscription which will have your billing information
Create a Resource Group in East US
Create a Speech Service entry
In your Speech Service entry, your API key can be found under Resource Management -> Keys and Endpoint
You can refer to Key creation, API key to TTS and AwesomeTTS API keys
Related
I hope you can help me in this problem
I have created a chatbot in the azure framework
Bot Framework Composer and I want to use it in WhatsApp Bussines
. My problem comes for the reason that bot framework composer
It still does not have a direct channel to whatsapp or any
platform like Twilio or Gupshup. I was recommended to use
the azure "DirectLine" channel that comes integrated, to take
the endpoint of my chatbot produced by azure when deploying it
in my group of resources and so with the keys of the channel that I
provides "DirecLine" to be able to interact with my chatbot. try
do the tests with the endpoint of my chatbot through Postman
but I have not been successful, despite following the documentation as indicated
microsoft, gives me an answer that is not authorized
I folow this steps
step 1
step 2
step 3
step 4
This is regarding the authentication error. To rectify the problem, here is the road map to follow.
Goto portal.azure.com
Search for Azure bot
Give the details of bot handle name and subscription. Mention the valid resource group name.
3. After creating the bot. Click on Channels where we need to create Direct Line access
Select the Direct Line
Click on New Site
Create a new site and key the key information
Now, using those keys we need to perform authentication operation.
Under the version in the above image, need to select 3.0, as Azure Direct Line authentication is functioning with REST API with 3.0 version of Direct line API
To enhance the authentication option, you can enable the Enhanced Authentication Option which is not functioning according to the current requirement in the case mentioned in question.
I have created a baisc QnA Bot using Azure services. But now after deploying the bot. I want it to be able to receive user mail id. So that I can give specific results on basis of the user currently using the bot.
Is it possible?
And what is the correct way of doing so.
Thanks in advance.
Please refer to the suggestion mentioned in this SO thread.
For details about how to obtain an access token for your bot, see Authenticate requests from your bot to the Bot Connector service.
Write directly to storage Azure blob transcript storage provides a specialized storage option that allows you to easily save and retrieve user conversations in the form of a recorded transcript.
I have a standard DocuSign account and I want to add an integration key but I am not able to add that key as there is no option to in my standard account to add the key. Further, I want to hit DocuSign API either through nodejs-sdk or postman to create and send an envelope with the use of the template. So, for this what should I do? Can anybody help, please?
Sounds like you're just getting started with the DocuSign eSignature API. Welcome! We have a variety of resources that you will find helpful.
I would start here on the DocuSign Developer Center.
To begin experimenting with our API, you'll first need to create a demo sandbox account. Within this account, you can provision your own integrator keys. Later down the road, you will follow our "Go-Live" process to transition your integration to our paid, production environment.
Once you have your account created, I would suggest you check out this quickstart code example.
That should get you started!
You should create a new developer/sandbox account to create an integration key. You cannot do that in production.
For node.JS we have a few different resources you can use, the most complete one is our code example "launcher" that can be used as a full app to try the code. We also have a quickstart that you an use without configuring the API authentication part.
I can see there are two versions of REST API endpoints for Speech to Text in the Microsoft documentation links.
https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/batch-transcription and https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-speech-to-text
One endpoint is [https://.api.cognitive.microsoft.com/sts/v1.0/issueToken] referring to version 1.0 and another one is [api/speechtotext/v2.0/transcriptions] referring to version 2.0. How can I create a speech-to-text service in Azure Portal for the latter one?
Whenever I create a service in different regions, it always creates for speech to text v1.0.
Any tips?
PS: I've Visual Studio Enterprise account with monthly allowance and I am creating a subscription (s0) (paid) service rather than free (trial) (f0) service.
Thanks,
Ozgur
All official Microsoft Speech resource created in Azure Portal is valid for Microsoft Speech 2.0
I understand that this v1.0 in the token url is surprising, but this token API is not part of Speech API.
So go to Azure Portal, create a Speech resource, and you're done.
If you want to be sure, go to your created resource, copy your key. That's what you will use for Authorization, in a header called Ocp-Apim-Subscription-Key header, as explained here
Demo:
Get your key on your created resource
Go to https://[REGION].cris.ai/swagger/ui/index (REGION being the region where you created your speech resource)
Click on Authorize: you will see both forms of Authorization
Paste your key in the 1st one (subscription_Key), validate
Close this window
Test one of the endpoints, for example the one listing the speech endpoints, by going to the GET operation on /api/speechtotext/v2.0/endpoints
Click 'Try it out' and you will get a 200 OK reply!
Understand your confusion because MS document for this is ambiguous. Per my research,let me clarify it as below: Two type services for Speech-To-Text exist, v1 and v2.
v1 could be found under Cognitive Service structure when you create it:
Based on statements in the Speech-to-text REST API document:
Before using the speech-to-text REST API, understand:
Requests that use the REST API and transmit audio directly can only
contain up to 60 seconds of audio.
The speech-to-text REST API only returns final results. Partial
results are not provided.
If sending longer audio is a requirement for your application, consider using the Speech SDK or a file-based REST API, like batch
transcription.
So v1 has some limitation for file formats or audio size. If you have further more requirement,please navigate to v2 api- Batch Transcription hosted by Zoom Media.You could figure it out if you read this document from ZM. You could create that Speech Api in Azure Marketplace:
That's the creation page for it :
Also,you could view the API document at the foot of above page, it's V2 API document.
Final tip:
v1's endpoint like: https://eastus.api.cognitive.microsoft.com/sts/v1.0/issuetoken
v2's endpoint like:
i want to use more requests for the Google Static Maps API then 25.000. So i have to take the option requests with a signature. I can't use the combination API key + signature secret for the authentification. I need a client ID. Where can I get this ID? I haven't fount the ID in my account.
Best regards,
Hannes
I have the answer: I'll need to request the lost client ID from https://google.secure.force.com/. But at first they must create an account for me. I hope this will work. ;)
Have you read Google Maps APIs - Guides?
UPDATE:
Your client ID and signature
Upon purchasing your Google Maps APIs Premium Plan license, you will receive a welcome email from Google that contains your client ID and your private cryptographic key.
Your client ID is used to access the special features of Google Maps APIs Premium Plan. In the sample below, substitute YOUR_CLIENT_ID with the client ID you got in your welcome email. All client IDs begin with a gme- prefix.
If you have lost your client ID or private cryptographic key, you can recover it by logging in to the Google Cloud Support Portal and clicking Maps: Manage Client ID from the links on the left of the page.