ION API Backend Service Item doesn't exist

Hello,

I trying to develop a new .Net web service application that would take data from M3 using ION API.

Currently i found a problem that i can't figure out.

I created authorization for backend service.

I tried it with GetUserInfo api and everything works fine.

When i try to call other api i get a OK status response with an error inside. Example api GetItmWhsBal Response: Item number 123456-TST does not exist

I tried the same call with same api parameters from swagger and i get all the data.

After swapping the bearer token with the one from swagger api call works and i can also get all the data.

What could be the problem with Backend Service authentication. Even if i use Web Application authentication there is no problems.

Maybe this is an issue with Service Account permissions, are there any settings to check what api calls or data this account can access.

Maybe there is some documentation to share about this topic

Thank you,

Find more posts tagged with

ION API Gateway

Accepted answers

sean-scanlon

Check the default company on the user associated with the service. Your error doesn't sound like an authorization problem, as you are able to access the API.

If you have different service users in different companies, perhaps that item does not exist in one company, but does in the other?

A lot of the API's allow you pass (lowercase!) cono & divi to set user context, but otherwise it's based on the user profiles defaults.

Just a guess.

All comments

sean-scanlon

Check the default company on the user associated with the service. Your error doesn't sound like an authorization problem, as you are able to access the API.

If you have different service users in different companies, perhaps that item does not exist in one company, but does in the other?

A lot of the API's allow you pass (lowercase!) cono & divi to set user context, but otherwise it's based on the user profiles defaults.

Just a guess.

Kevin Heiman

Accessing the API is separate from being authorized to invoke the API. Best way to test is to use Postman and the same credentials you are using in .net.

The service account has an associated user that it is proxying in the application. It must have the fine grain authority to access resource that the API requires.

You can also look at the API Gateway monitoring for some detail (more logging is coming ina release or two).

You can review the service account and associate user in IFS Service accounts. Suggest you use the new Service Users capability going forward. Is the associate account disabled? Does it have the correct roles to access the resources?

First test with Postman wiht the same credential using backend service auth.

unknown

Thank you, this was the problem

Copyright © 2025 Infor. All rights reserved.