ION Connection Endpoint for Inbound BODs On-Prem

Andrew Vieira · 2025-05-12T15:53:08+00:00

There was an error rendering this rich post.

I am trying to fix an ION connector for an on-prem WebUI system so that inbound bounds will be processed. I think the current IMS endpoint is incorrect because when I try to query it from Postman, I get a 404 error. I am also not getting any acknowledge BODs back when a BOD is sent into the system.

Outbound BODs do work.

Is there a way to troubleshoot the issue?

Find more posts tagged with

Accepted answers

All comments

Kevin Heiman

Andrew can you further clarify the scenario? I read it as you have a on Prem Web Application that has added client code to support writing to a Cloud IMS endpoint. That onprem Application gets a 404. You also attempt to connect via postman and same error.

You also mention that BODs are being sent from MT to the onprem Web application using IMS. So the web app has a API server for IMS that is working, but the API client o MT is failing.

Does ping from both scenarios work to resolve the host?

Are you able to test other interfaces in Postman?

Are you successfully getting a token ?

Andrew Vieira

Hi Kevin,

I think your summary is correct. The specific BOD I'm trying to get working, but is failing is Process.SupplierInvoice.

I can ping the on-prem server. I'm not sure what I need to Ping for the second scenario.

For other interfaces, I can call the SXAPI rest APIs with Postman. For example:{url}/test/rest/sxapirestservice/sxapioefullordermntv5 works.

I think there's something wrong with the specific endpoint I'm using, but I'm not sure what it is.

Kevin Heiman

The important part is "for other interfaces I can call the SXAPI rest…" that would mean you are able to get a token, and resolve the address of the MT API server in API Gateway.
I presume you follow the same process for the Infor OS ION suite call via the API gateway.
The 404 would imply you are not using the same host:port , which you should be getting from the .ionapi file, or that you are not building the correct url string for the service.
If it is failing in PostMan, that would be a simple place to start to resolve.
Try a SXAPI or a simple Infor OS Ping service to make sure you are getting the server and authentication parts successfully. Then add a simpler URL to another OS suite. Then focus on the IMS one.
Did you download the code samples from Infor for the IMS API client?
Once you get a connection you will see the activity in API Gateway.

Also see the documentation suggestions: https://docs.infor.com/inforos/2025.x/en-us/useradminlib_cloud/default.html?helpcontent=ioncedg_cloud_osm/uxc1624890457818.html

Brandon Watson

Andrew - For SX.e on-prem, the url will be below. Assuming the PAS is running on 8080. You could also use the HTTPS URL, which would be the same as the RESTAccessURL SASBR. not sure where you are getting the 'test' part of your url from.

http://servername.domain.com:8080/rest/serviceinterface/service

https://servname.domain.com/rest/serviceinterface/service