topic Re: Webex API Post status code 400 in Webex for Developers

Webex API Post status code 400

Mikey Boy — Thu, 27 Jul 2023 08:39:13 GMT

Hi, I am trying to use the API from within Node-red currently. However, I am unable to get a successful connection and I am always receiving status code 400:

"{"message":"The request could not be understood by the server due to malformed syntax.","errors":[{"description":"The request could not be understood by the server due to malformed syntax."}],"trackingId":"ROUTER_64C22C53-E762-01BB-0127-0AFDD9310127"}"

I have tested the connection within Talend and I can successfully authenticate and get a status 200 response.

The only difference I can see in the headers for the successful request is that content-encoding is gzip. But the requests from node red are going as chunked?

date: "Thu, 27 Jul 2023 08:35:35 GMT"

content-type: "application/json"

transfer-encoding: "chunked"

connection: "close"

via: "1.1 linkerd, 1.1 linkerd"

trackingid: "ROUTER_64C22C53-E762-01BB-0127-0AFDD9310127"

server: "Redacted"

x-content-type-options: "nosniff, nosniff"

vary: "accept-encoding"

strict-transport-security: "max-age=63072000; includeSubDomains; preload"

x-node-red-request-node: "acea2c94"

Regards

Re: Webex API Post status code 400

Janos Benyovszki — Thu, 27 Jul 2023 11:30:05 GMT

@Mikey Boy not sure what request you are exactly making, but the body syntax might trigger that error too. I would recommend doing some testing first in Postman https://www.postman.com/ and if that works, you can use the code generation function https://learning.postman.com/docs/sending-requests/generate-code-snippets/ there to have a base script that you can implement in your code.

Re: Webex API Post status code 400

Mikey Boy — Thu, 27 Jul 2023 15:00:56 GMT

Thanks, I actually managed to solve it, I had to insert the room ID within a the main payload, I was trying to insert it as part of an object field.