Alteryx Soap API Call error message

[vaibhav3339]

<faultstring>Processing error occurred. Unexpected end of data reading bytes. Expected 514 but EOF after 0</faultstring><detail><wd:Processing_Fault><wd:Detail_Message>Unexpected end of data reading bytes. Expected 514 but EOF after 0</wd:Detail_Message><faultstring>Processing error occurred. Unexpected end of data reading bytes. Expected 514 but EOF after 0</faultstring><detail><wd:Processing_Fault><wd:Detail_Message>Unexpected end of data reading bytes. Expected 514 but EOF after 0</wd:Detail_Message>

Can someone let me know what this error means?

I am using download tool to call integration process through Soap API call.

[davidskaife]

Similar to your previous post i suspect this is more of a soap issue, not an Alteryx issue. You really need to pose this question on a forum related to the application you're trying to access, or look through their API documentation...

It reads like the data being retrieved wasn't all there, so is erroring out as its expecting 514 bytes but got 0. To troubleshoot you really need to look at the soap side of things

[abacon]

Have you gotten the api call working on another tool like postman?

[vaibhav3339]

Yes, the same API call is working on Postman.

[apathetichell]

Hey @vaibhav3339  - the thing is - these posts are not about Alteryx. They are about your SOAP call. They are not things we can fix. You have to dive into your payload and compare the differences between what Postman is sending and what is in your payload body in Alteryx. This is not something we can help you with. Just make sure you have your soap header set up as content-type in your download tool. After that --- it's really on you. The message you are seeing says something is different between Alteryx and Postman... What is it? We can't tell you without seeing the payloads -- and to be blunt - this is your job.

[vaibhav3339]

The thing here is the same API payload is working on Postman but not working on Alteryx. In the header we are passing the Access token for authorization. That access token is passed as an variable in the header of download tool. Code is exactly the same and no difference but still getting the above error which is not understandable also I made sure that there are not extra spaces or something like that in the payload body.

[apathetichell]

We can fix this by

1) wasting our time stabbing at things in the dark. (current method)

2) you telling us what the api is - and someone saying 'hey! I've build something for it' (middle ground)

3) you providing both your postman and your alteryx payloads. copy and paste directly. (easiest method)

3) is the easiest but most likely to expose secure data. Back to my original point ---- I am close to 95% sure something is different between your postman payload or your alteryx payload either in:

1) endpoints.

2) payloads

3) headers.

Most likely it is 2. Most likely something you think you are passing in - you are not or vice versa or there is an encoding difference.

[vaibhav3339 · Accepted solution]

This issue if fixed now. I added Content-Type in header and it started working.

[apathetichell]

Hey - I told you to do that on Tuesday - can you accept my earlier answer as a solution?