Skip to content

Commit 2be5b13

Browse files
authored
Update migrate-to-v3.md
1 parent 30ca871 commit 2be5b13

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/ai-services/translator/text-translation/how-to/migrate-to-v3.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,10 +54,6 @@ Microsoft Translator Translation V2 accepted and returned data in XML format. In
5454

5555
This change affects several aspects of an application written for the V2 Text translation API. As an example: The Languages API returns language information for text translation, transliteration, and the two dictionary methods. You can request all language information for all methods in one call or request them individually.
5656

57-
The languages method doesn't require authentication; by selecting the following link you can see all the language information for V3 in JSON:
58-
59-
[https://api.cognitive.microsofttranslator.com/languages?api-version=3.0&scope=translation,dictionary,transliteration](https://api.cognitive.microsofttranslator.com/languages?api-version=3.0&scope=translation,dictionary,transliteration)
60-
6157
## Authentication Key
6258

6359
The authentication key used for V2 is accepted for V3. You don't need to get a new subscription. You can mix V2 and V3 in your apps during the yearlong migration period, making it easier for you to release new versions while you migrate from V2-XML to V3-JSON.

0 commit comments

Comments
 (0)