The error message pretty much tells you what went wrong. The returned message that it received as a result of its call simply did not start with the curly bracket "{". If the first character is not a curly bracket, then it is deemed that it is not a JSON object it expected thus it stopped processing.

You will need to check with the provider of the call you are making to. Make sure that it whitelist your Joget Workflow domain if there's such feature in place for them and/or you are making the correct call with the necessary parameters/payload expected by the provider.

Thanks Walter - that's what I thought but the response should start with "{" (even errors come back in standard json objects). I know through testing the same POST call with another tool that the response always starts with "{". It is somewhat hard to track because I cannot see the actual POST call that Joget assembles from the different hash variables - any tip on how I would be able to see what Joget actually sends out? I am using escaped (?url) form hash variables - is it possible that something goes wrong when they are replaced?

Hi guys,

I did further testing and found the following problems:

When I pass all the parameters in the url in the POST Tool it seems that the request reaches the server. Because if I test it a second time in another tool (Postman) then I get "code already used"for a one-off code.
When I pass the parameters under "parameters"in the POST Tool then the request doesn't seem to reach the server.

Secondly, the same error as outlined above exists in both instances. I simply cannot get the data back into Joget - something seems to go wrong when the response is parsed (response definately starts with  "{" as outlined above.

Could you please test wherever the tool works for you guys with HTTPS requests?

Cheers,

Eric

Curious: The JSON Post Tool works with the OAuth slack API all the way through. It doesn't work with the Asana Token endpoint or to make a call against the Dropbox API with Authorization through a Bearer token (both OAuth flows). Julian Anders, any ideas what could go wrong? The exact same requests work in Postman. Might be a CORS or pre-flight issue?

I just re-tried calling some of these APIs with the new JSON Tool (Joget 6 Beta2) and it looks like this works now.Haven't finished testing all of them but I'll mark this as resolved since the error this thread was about does no longer occur.

Great job - thanks guys!