diff --git a/articles/ai-services/speech-service/swagger-documentation.md b/articles/ai-services/speech-service/swagger-documentation.md
index 084bf208d78..c26f0a1381f 100644
--- a/articles/ai-services/speech-service/swagger-documentation.md
+++ b/articles/ai-services/speech-service/swagger-documentation.md
@@ -22,7 +22,7 @@ The Speech service offers a Swagger specification to interact with a handful of
 
 ## Generating code from the Swagger specification
 
-The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.1/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1.
+The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.2/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1.
 
 You need to set Swagger to the region of your Speech resource. You can confirm the region in the **Overview** part of your Speech resource settings in Azure portal. The complete list of supported regions is available [here](regions.md#regions).