Infor ION API - Infor CSI

Hi All,

I'm just wondering how I'd go about integrating the CSI / Mongoose REst API into Infor ION API.

I can't see any easy to follow guide in the documentation that I've got acces too, though maybe I've looked over it by mistake.

I see that when I go to add an API I see a bunch of Infor Branded Products (Included Infor Mongoose which I've tried to configure) but I believe that I'm doing it incorrectly.

I've seen a video of someone with a CSI API in the Infor OS API Suite, as the cion matched that of our Ion hosted CSI Session.

Please shout out if I need more information, just looking to make some headway with things, but so far have come up short.

Cheers,

Jamie.

Find more posts tagged with

General Discussions

Accepted answers

All comments

unknown

Once you follow the steps in this video, you can use the CSI v2 API via Postman if you are using SaaS:

https://www.youtube.com/watch?v=RJCEsnzSdIM&list=WL&index=4&ab_channel=InforOS

If you are on-premise, that's a whole other ball of wax and really there should be no need to go through ION, because you can setup your network to allow direct access to the CSI APIs. You don't gain anything by going through the ION API (other than OAuth authentication). It is just passing through your request to the CSI API. However, once you do go through the process of setting up OAuth, You can access the other ION APIs for Document and Workflows.

unknown

There could be other motivations than OAuth, to use your target API via the ION API gateway - mainly to leverage one of the many policies that the gateway offers, eg: to change your request or response using the transformation policy in such a way that your server or client is happy with Or use the quota policy to limit usage etc.

unknown

For the author's stated intent, accessing the CSI API, those would be fringe benefits, but not really applicable to his use case. But yes, as I indicated, there are other benefits to using the ION API for non-CSI API related tasks.

unknown

In fact, the author's stated intent/ use cases are very generic, right!? I just wanted to clarify that OAuth2 is not the only value add of ION API Gateway.

unknown

Hi Tim,

Thanks for the response. We are unfortunately running On-Premise at the moment (9.01).

I wanted to configure the API to work via OAuth to at least have some understanding of how it worked.

At the moment it looks like once the API Grants a security Token, that token seems to have a very long life. I'm unsure of the exact lifetime of it, or if that's configurable or if it would even be prudent to worry about that! We're looking at using the api to integrate with an application that is being developed so security is something that would be valued.

I suppose the other way that I would be looking at it would be if I host it through ION (Which is also located on prem) Then we wouldn't have to open the CSI API to external networks. Hopefully that makes sense?

unknown

It's half-a-dozen one way, half-a-dozen another. I thought you had said on-premise before which is why I threw in my caveat. Your on-premise setup is not guaranteed to be configured the same as a SaaS instance, so some of the video's settings may not be applicable or could be different than shown as a result. The OAuth is based on how your Infor OS and ADFS systems were configured, which is a whole other conversation not easily covered in a discussion posting and not one I could talk you through because I have never gotten it working in a local development environment myself.

Even if you got the OAuth to work, you technically are still exposing the CSI APIs, just behind the Infor OS proxy, rather than direct. Depending on how your clients are accessing CSI, you probably have those exposed anyways, because the Smart Client uses the same IDO Request Service as the REST APIs. That's why SaaS has them exposed as well, as well as backwards compatibility with third-party apps and integrations that rely on the CSI API.

unknown

Jamie, Token expiry time is configurable per authorized app. Min = 15 mins; Max = 2 hours. Before the token expires, you can request a new token by supplying the refresh token. The refresh token's lifetime can be set to long durations. See the screenshot below (from the authorized app details page). The ION API admin guide as well as the Github page referred in the YT video posted above has a section on the OAuth2 token management.

unknown

Hi Tim,

Thanks again for your response. I don't hold much hope of managing to get it working if you were unsuccessful, but I'd be remiss if I didn't at least try!

I might be missing something with regards to the video that you sent. It looks incredibly useful for how I'm going to want to call that CSI/Mongoose Rest API, but at the moment I don't even have the Mongoose REST APIsitting as an available API. I've tried configuring it using the Host Name: ourUtilityServer/IDORequestService/MGRestService.svc and leaving the Port and context blank. The Default Tenant ID i've provided as infor.

The Target Endoint Security I've set as API Key.

Key Mode Header.

Key Name: Authorization

Key Value: Auth Token copied from postman

When clicking on the documentation tab, I get an error "The application has encountered an error. Try again or contact your administrator. (Error Code 500)"

Looking at the Request URL in Chrome shows it's trying to access the following:

IONSERVER:7443/infor/MONGOOSE/IDORequestService/MGRestService.svc/ionapi-doc

This might warrant it's own post to be honest, but I was hoping to actually configure the rest API to be visible inside ION before I proceed.

I've also found the attached in a video, which might be a newer version of ION that we need toupdate to, that looks to have the CSI API Working as Infor Provisioned.

Copyright © 2025 Infor. All rights reserved.