{"id":83195,"date":"2018-06-15T00:01:27","date_gmt":"2018-06-15T07:01:27","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/?p=83195"},"modified":"2019-02-18T09:09:56","modified_gmt":"2019-02-18T16:09:56","slug":"windows-powershell-and-the-text-to-speech-rest-api-part-4","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/windows-powershell-and-the-text-to-speech-rest-api-part-4\/","title":{"rendered":"Windows PowerShell and the Text-to-Speech REST API (Part 4)"},"content":{"rendered":"

Summary<\/strong>: Send and receive content to the Text-to-Speech API with PowerShell.<\/p>\n

Q: Hey, Scripting Guy!<\/p>\n

I was playing with the Text-to-Speech API. I have it almost figured out, but I\u2019m stumbling over the final steps of formatting the SSML markup language. Could you lend me a hand?<\/p>\n

\u2014MD<\/p>\n

A: Hello MD,<\/p>\n

Glad to lend a hand to a Scripter in need! I remember having that same challenge the first time I worked with it. It\u2019s actually not hard, but I needed a sample to work with.<\/p>\n

Let\u2019s first off remember where we were last time. We\u2019ve accomplished the first two pieces for Cognitive Services Text-to-Speech:<\/p>\n

    \n
  1. The authentication piece, to obtain a temporary token for communicating with Cognitive Services.<\/li>\n
  2. Headers containing the audio format and our application\u2019s unique parameters.<\/li>\n<\/ol>\n

    Next, we need to build the body of content we need to send up to Azure. The body contains some key pieces:<\/p>\n