BUG: Content-Type: application/json
Hello, since today's morning a bug has emerged in every project spontaneously regarding API call's header: Content-type: application/json - it seems that if we use this header it double fills under the hood -> hence the API call fails.
2 Replies
👋 Heads-up on the Content-Type issue
A change that went live this morning makes Voiceflow automatically add a default
Quick workaround 1. Open your Custom Action / API steps. 2. Remove the manually-added
• Keep the Body Type set to JSON – Voiceflow will attach the correct header for you.
• If you really need to set the header yourself, switch Body Type to Raw and include the header once in the Headers table. That will stop the duplicate header and the calls will succeed again. The engineering team is aware of the behaviour change and is monitoring feedback, but the flows will work normally with the adjustment above. Docs reference: https://docs.voiceflow.com
Content-Type header whenever the Custom Action (API) step’s Body Type is set to JSON. If you also manually add Content-Type: application/json in the step’s Headers section, the request now carries the header twice and some APIs will reject it.Quick workaround 1. Open your Custom Action / API steps. 2. Remove the manually-added
Content-Type row from the Headers table.• Keep the Body Type set to JSON – Voiceflow will attach the correct header for you.
• If you really need to set the header yourself, switch Body Type to Raw and include the header once in the Headers table. That will stop the duplicate header and the calls will succeed again. The engineering team is aware of the behaviour change and is monitoring feedback, but the flows will work normally with the adjustment above. Docs reference: https://docs.voiceflow.com
Aah, if this is true, then this answer is really spot on - gonna try rn
Wow really cool! @Tico | Voiceflow Assistant thanks Tico 💪