Help Needed with Inconsistent POST API Responses via make.com

Hi everyone,

TLDR: I'm experiencing inconsistency with POST API calls via make.com in my Voiceflow project. Despite identical setups, calls intermittently return either a successful (Status 200) or failed (Status 400) response, primarily differing in the content-length field

I've been working on a project using Voiceflow and have come across an error with POST API calls that I'm making through make.com. Initially, everything works perfectly with a successful response, but subsequent attempts are hit or miss, even though I'm not changing anything between calls. Here are the details of what I'm seeing:

Successful Call: - Status: 200 - Content-Length: 8 - Example Response:

json { "VF_STATUS_CODE": 200, "VF_HEADERS": { "content-length": "8", // other headers... } }

json { "VF_STATUS_CODE": 200, "VF_HEADERS": { "content-length": "8", // other headers... } }

Failed Call: - Status: 400 - Content-Length: 48 - Example Response:

json { "VF_STATUS_CODE": 400, "VF_HEADERS": { "content-length": "48", // other headers... } }

json { "VF_STATUS_CODE": 400, "VF_HEADERS": { "content-length": "48", // other headers... } }

I don’t understand what the problem could be since the only apparent difference is the

content-length

content-length

. Could you perhaps shed some light on why this might be happening or guide me on what steps I could take to fix this? Any insights or tips would be hugely appreciated!
The screenshots of the problem are attached:
Picture 1: My API call from make.com as web-hook
Picture 2: My initial successful API call:
Picture 3: My second failed call (look at the time difference between picture 3 and 2, I truly did not change anything in between)

Thanks so much for your help!

Best,

Oscar

Voiceflow Partners•2y ago•

3 replies

skinny-azure

Help Needed with Inconsistent POST API Responses via make.com

json { "VF_STATUS_CODE": 200, "VF_HEADERS": { "content-length": "8", // other headers... } }

json { "VF_STATUS_CODE": 200, "VF_HEADERS": { "content-length": "8", // other headers... } }

Failed Call: - Status: 400 - Content-Length: 48 - Example Response:

json { "VF_STATUS_CODE": 400, "VF_HEADERS": { "content-length": "48", // other headers... } }

json { "VF_STATUS_CODE": 400, "VF_HEADERS": { "content-length": "48", // other headers... } }

I don’t understand what the problem could be since the only apparent difference is the

content-length

content-length

Help Needed with Inconsistent POST API Responses via make.com

Similar Threads

Help Needed with Inconsistent POST API Responses via make.com

Similar Threads

Similar Threads

Similar Threads