API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret

Question: I have a CAT* tool which is asking me for the Client ID and Client Secret credentials to use my Microsoft Translator subscription. It isn't working now. What do I do?

Answer: The Microsoft Translator API switched the method of authentication in October 2016, and turned off the Client ID and Client Secret method on May 1, 2017. The new authentication method is using a key.

You will need to obtain/download an updated version of your CAT tool from the software provider.

The updated version should ask you for your Microsoft Translator Text API subscription key. The steps of obtaining a Translator Text API subscription key in the Azure portal are explained here.  

You will then copy one of the two keys you receive in your Translator Text API subscription account into the "subscription key" or similarly labeled field in your software. As an example, here the makers of the CAT tool "Fluency" explain how this works with Fluency's software.

*CAT = Computer Aided Translation

For developers of CAT tools:
If you are a developer of CAT tools, or a developer of any tool that offers translation functions to users: The most convenient method for your users to consume translation is if the user doesn't have to sign up to the Microsoft Translator API separately. You can offer translation functions in your product under your own subscription, and pass on the consumption cost to your users. Use the Microsoft Translator Contact Us form if you have any questions.  

Originally published May 17, 2017


  1. Announcements: Microsoft Translator Moves to the Azure portal
  2. API - Translator Data Centers
  3. API and Hub: Confidentiality
  4. API - Translator Text: How to report an issue with the API
  5. API - Translator Speech: Microsoft Translator Speech API references
  6. API - Translator Text / Speech: Get a report of your consumption
  7. API - Translator Text / Speech: Using the API key directly in the call. No more token.
  8. API - Translator Text / Speech: Why are there two keys for my API subscription?
  9. API - Translator Text: Hybrid Neural Machine Translation
  10. API - Translator Text: Using Neural MT Systems
  11. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  12. API - Translator Text: Limits
  13. API - Translator Text: How Microsoft Translator counts characters
  14. API - Translator Text: Gender selection in the Speak() method
  15. API - Translator Text: Trados plugin for Microsoft Translator
  16. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  17. API - Translator Text: European datacenter
  18. API - Translator Text: Languages detected by the Detect() method
  19. API - Translator Text: Using the Collaborative Translation Framework (CTF)
  20. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  21. API - Translator Text: Microsoft Translator with IP filtered firewalls
  22. API - Translator Text: Profanity filtering in the TranslateArray() method
  23. Hub: API Preview released
  24. Hub: Translator Hub Resource Guide
  25. Hub: August 2016 Release notes
  26. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  27. Hub: Capacity of custom Microsoft Translator Hub systems
  28. Hub: Building a custom system using a dictionary only
  29. Business Applications: Security and Privacy in Microsoft Office Products

Feedback and Knowledge Base