M3 API in ION API returns 200 when no record is found

When calling an M3 API and the API is not successful in retrieving the record ION API returns 200. Because of this our data flows don't fail and Sync.Error BODs are not created. Is there any workaround for this? By API standards return code should've been 404

Find more posts tagged with

ION Workflow

Accepted answers

Legacy Contributor

API Gateway is a pass-through brokering/ management layer. By default it will pass through the response thats coming from the target API. Ideal scenario in this situation is to raise an enhancement request to M3 team to send a different HTTP code when empty result set is returned.

Having said that, the simplest option here is to wrap your M3 API via an API Flow. You can check if the records are empty inside the flow and if so make it return a 5xx code. From your data flow you can then call the API flow instead of the M3 API, which should return the 5xx code per your needs.

All comments

Legacy Contributor

Anders Karlsson

At the moment this is the M3 API behavior as it is defined in the API guide.

You are welcome to raise an Enhancement request for the M3 Product in Infor Concierge.

Otherwise you can follow Vignesh proposal and based on nrofSuccesfulTransaction decide the status code you like with an API Flow.

Rene Bottern

I do NOT think changing the behavior is good suggestion, since I believe MANY Customers have built their solutions based on current logic/functionality.
I am using the below fields to determine if there was a Success OR Failure.

Legacy Contributor

Of course, if a standard API behaviour is going to change, it cannot break the backward compatibility. We would follow the standard practices and would release it as a new version or an optional input indicator that can guide the response flavour.

Rene Bottern

The suggestion above was to change the "Response Code" to 404 instead of 200, this is a change in my mind.

DM9346

Yes we have seen these fields. The problem is that there is no way to trigger a controlled error via Error BOD in dataflows and even workflows.

Vignesh's suggestion is a good workaround but it's still not in it's native form i.e. all M3 APIs must be wrapped around an ION API flow.

The always 200 result no matter what happens in my opinion is not industry standard. What happens when M3 API cannot be reached will we still get 200 response? This is contrary to ION APIs if you query a document flow that doesn't exist you get 401.

I do hope a new version comes up wherein errors will not be logged as 200. That or introduce a way to trigger an error bods in data flows and workflows.

DM9346

Hi Vignesh,

Been trying to accomplish this but the API of the API flow has been returning error. Can you confirm if this is what you meant by using the API flow.

The no branch gives a 404 API return code while the yes path is the 200 return code.

I can't seem to find any documentation(checked docs.infor) or example on how to do the script in the filter tab.

Copyright © 2025 Infor. All rights reserved.