Unsupported content type

Getting response as “Unsupported content type” while making a request using client.request in my frontend code.
Below attached screenshot of request.json and invoke template
invoke template :

Request.json :

Additionally, I receive the error mentioned below when I pass an object without JSON in the body.

Error : Error in establishing connection

Hi @Vrushali_Ambre,

The body property should be a JSON value. That is expected.

For the unsupported content response, what content type is expected in the response? Please check the supported content types for the response in the following post.

@Vrushali_Ambre For the error, the content-type header is verified in the response. Can you please share what is the exact Content-Type header value in the response?

Hi @Raviraj

The content type received is ‘application/octet-stream’. It also works fine in Automation with the same API.

@Vrushali_Ambre This response type of “application/octet-stream” is not currently supported.

If you can share more information about the purpose of this API and more information for us to consider, we can record it as a feature request so that our team can consider it to validate your request.

Hi @Raviraj

I am attempting to call a third-party API that provided me with base64, which I wish to display in Freshdesk. The content type is “application/octet-stream.”
And I’m using the same third-party API in the automation of Freshdesk, where it works fine.

@Vrushali_Ambre We have shared the use case with the team. You also have a support ticket. If you could follow up there, our team would be able to share any ETA if available for this feature request.

Automation in Freshdesk and Marketplace apps run on different systems and work differently. Since Marketplace is more open for all kinds of apps, it may be more restrictive with the content type to provide security for the apps.