Skip to main content
jcyoungkin
jcyoungkin
Contributor ⭐️⭐️⭐️
October 30, 2025
New Idea

Allow API Calls to Support Encoding for Content-Type

Related products:CS Other Features
  • October 30, 2025
  • 1 reply
  • 30 views

Recently we found out that calls to the GS API don’t support encoding for the Content-Type header. An error comes back looking like the following:

 

Content-Type: application/json; charset=utf-8 for the event 'event_name_here' does not match the expected Content-Type: application/json.

 

Working with GS Support they’ve let me know the engineering team has logged this as an enhancement request and plan to begin work on it in the second week of November, and it might take at least one quarter to deploy this into production.

It was then mentioned to create an enhancement request here in order to get updates on its deployment, so here is that request.

  • Ticket ID: 431427

Hoping get an update on when this enhancement has been deployed.

Cheers!

    1 reply

    TexasTacos21
    Contributor ⭐️
    June 1, 2026

    Upvoted. I had this same issue while trying to connect Zendesk to Gainsight via webhooks. I had to use a middleware solution (Cloudrun Function intercepts the webhook and sends to Gainsight) simply because GS would not accept the content-type, nor could it be adjusted in Gainsight. 

    Terms & ConditionsAccessibility statement