Azure Translator
An Azure service to easily conduct machine translation with a simple REST API call.
363 questions
Microsoft Translator Service API suddenly stops authenticating
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 86%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
MNF
0
Reputation points
Microsoft Translator Service API suddenly stops responding to API calls and starts giving 401 Status code although there is no billing problem or either the free quota is also not emptied. Even though I have a subscription for Pay-As-Go activated even if the service free limit gets hit. Please help why the error is occurring.
Fixes i tried-
tried creating new resource with new keys
{count} votes
-
romungi-MSFT 43,656 Reputation points Microsoft Employee2023-12-22T13:13:01.3266667+00:00 @MNF Could you add a code snippet of how the API was called?
I would recommend to check through REST API using postman if the keys are valid before regenerating keys or creating a new resource. This simple script should also work with your resource, ensure the region is added if you are using a multi service account though.
-
romungi-MSFT 43,656 Reputation points Microsoft Employee
2023-12-27T05:32:40.47+00:00 @MNF Did the above suggestion help to check if the keys are working with POSTMAN?
-
Michael John Pena 160 Reputation points MVP2023-12-28T07:16:09.0933333+00:00 The 401 status code indicates an Unauthorized error. This usually means that the API is not able to authenticate the provided key. Even though you have created a new resource with new keys, this problem could persist because of several reasons.
Here are few things you might want to check:Key validity:
- Ensure the keys are valid (which I guess you already tried)
- Region: While making the API call, ensure that you're using the correct region for your Azure service. The region should be the same as what you have selected while creating your Azure resource.
- Headers: Ensure that you're passing the subscription key correctly in the header of your HTTP request. The header should be 'Ocp-Apim-Subscription-Key'.
- Endpoint: Check if you're using the correct endpoint URL for the API.Here is a sample code to call the Microsoft Translator Text API:
Sign in to comment