ION API Connection point fails when testing with "Not found and response body"

I have written a .Net 6 webapi service that receives a custom BOD. I have added the service to the ION API with anonymous auth (for now). The web service doesn't do anything yet and just returns an OK - 200 response.

The connection point is set to "XML from BOD" to parse just the Noun portion.

Viewing the request parameter, I can confirm only the noun portion is displayed:

The following error occurs:

Making the same call in the ION API or Postman works as intended.

I've been stuck on this for hours now. Any assistance would be appreciated.

Regards

Find more posts tagged with

ION Connect

Accepted answers

All comments

unknown

Hi Dusty,

when I looked to the screenshot I observed that the curl command from ION API has parameter accept: "text/p;lain" but that in the screenshot of your test App it says accept: "application/xml".
Not an expert in ION API, nor sure if relevant, but in similar situations matters like that was causing issue.

BR/Jan

dustin-hughes

Thanks Jan. I corrected that but still the same issue. It works in ION API and fails in ION.

unknown

Dusty, Is your proxy and target authentication both set to anonymous? If it is then please change the proxy authentication to OAUTH 2.0. Re-index the IONAPI metadata. Wait for this to complete. Then try your API connection point again.

dustin-hughes

Thanks Hari. Unfortunately, the same issue after changing the proxy security and re-indexing.

unknown

Hello Dusty, is your problem solved in the meanwhile. Some thoughts nonetheless, looking into the error:

Obviously the request constructed by the API connection point doesn't seem to fulfil the target API's expectations. Did you check the ION API Monitoring UI to analyse this particular API call and see if there are more clues on the failure?
On your Target API server side, do you see the requests coming in and is there a way to debug/ analyse why it is rejecting the request?
Can you attach the Swagger documentation of your API? Perhaps a missing header parameter or other parameter mismatch? Did you also map some input parameters in the "Request Parameters" tab?
Can you confirm that the "Noun" section of your BOD is still a well formed XML with no forbidden characters etc?
I see that your BOD input is missing an ApplicationArea section. I don't think that matters. But it does no harm to include that and repeat your test.

dustin-hughes

Hi Vignesh

Thanks for your response. I still have the problem. However, I implemented a workaround using a SQL CLR assembly to call my web service from a SQL stored procedure. But I still need to solve this.

We have just gone live at my client so I haven't had a chance to spend time on this issue.

Regarding your questions. I should have time to get you some answers later today but for question 5, the reason only the noun portion is shown is that I have "XML from Bod" format selected on the connection point.

This takes the full BOD as delivered by ION as input:

Clicking on the request parameters on the test dialog you'll see that ION strips out everything except for the noun.

I have created another service to accept the full BOD, but I'm still having the same issue.

What I am looking into is the ION Technical Guide specifies:

Regards

dustin-hughes

Hi Everyone

I have found the issue but I'm not sure why it is happening. Could be an issue with my swagger.

I have this path defined in my swagger:

Below is the IIS log. The green highlighted entries are successful calls. The first was with postman and following 2 calls where by testing with the swagger interface within the IONAPI.

The red entries are tests made from the ION API connection point which fail.

I'll play with the swagger to see if I can fix the issue.

dustin-hughes

I have got to a point where I can get my service to work with either the IONAPI swagger or the ION connection point. I think this is a bug as the IONAPI connection point and the IONAPI swagger test should work exactly the same.

My swagger now contains a path for ION and another for the IONAPI. The first is the ION API and the second for the ION connection point:

In the IONAPI there will be two paths. The top one will work, and the bottom will fail.

In the ION connection. There will be two paths, the short one will work. The long one will fail

This will work for but still feels like I'm doing something wrong.

Copyright © 2025 Infor. All rights reserved.