topic Re: Imagine preview not displaying (webex rest api) in Webex for Developers

Imagine preview not displaying (webex rest api)

Josh Flori — Wed, 21 Sep 2022 15:13:46 GMT

I follow the simple attachment post request here and post a jpg or pdf into a webex chat.

The preview does not display. But previews DO display when inserting manually.

Results are consistent across time.

Thoughts?

Re: Imagine preview not displaying (webex rest api)

Jeff Marshall — Wed, 21 Sep 2022 18:52:39 GMT

Are you sending the attachment using a URL or sending as a local file upload?

Re: Imagine preview not displaying (webex rest api)

Josh Flori — Wed, 21 Sep 2022 19:00:57 GMT

Local file upload

Re: Imagine preview not displaying (webex rest api)

Josh Flori — Wed, 21 Sep 2022 19:00:57 GMT

Local file upload

Re: Imagine preview not displaying (webex rest api)

Jeff Marshall — Wed, 21 Sep 2022 19:47:34 GMT

That should work and this is a curl example where the .jpg file did render the preview correctly.

curl --location --request POST 'https://webexapis.com/v1/messages' \ --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \ --form 'files=@"/Users/jeffmar/Downloads/Sample_Icon.jpg"' \ --form 'markdown="File sent using curl"' \ --form 'toPersonEmail="user@example.com"'

Re: Imagine preview not displaying (webex rest api)

Harry Pickthall — Thu, 06 Oct 2022 09:31:02 GMT

I'm having a similar issue working in Powershell, the image does send but no preview. Any suggestions?

$uri = "https://api.ciscospark.com/v1/messages" $filePath = "C:\Users\Harry\Documents\WebexTestImage.png" $file = Get-Item -Path $filePath $form = @{ toPersonEmail = "MYEMAIL" markdown = "TestImage" files = $file } $params = @{ Method = "Post" Uri = $uri Form = $form Headers = @{"Authorization"="Bearer $Ciscobottoken"} } Invoke-WebRequest @params

Re: Imagine preview not displaying (webex rest api)

dstaudt — Thu, 06 Oct 2022 19:47:16 GMT

Running this request and looking at the raw HTTP, it looks like the Content-Type of the file part is set to "application/octet-stream" (i.e. a default/non-descript binary file type), whereas I suspect Webex is expecting this to be "image/png" if you want PNG image preview treatments.

The Curl and Python samples in the Webex docs re Message Attachments seem to indicate indicating the mime-type specifically like this is expected.

A bit of research didn't turn up a way to set a custom Content-Type for sub-parts using the PowerShell IWK -Form mechanism you're using. If that's not possible, may need to construct the message using more "manual"/specific mechanisms, e.g.: https://get-powershellblog.blogspot.com/2017/09/multipartform-data-support-for-invoke.html