Can the IONAPI Request activity be used with IMS via API gateway connection point?
I keep getting
{ "status": "FAIL", "code": 471, "errors": "Invalid client id provided"}
Can you provide some more context on what you're trying to accomplish?
I am trying to send a bod document to ION using IMS and RPA . It seems like when the ION RPA request activity executes it uses the internal client id. RPA—→ Executes ION API request —> API request executes —> IMS — IMS send BOD to ION —→ Consumed by LN .
Thanks. Unfortunately, I'm not familiar with RPA.
It seems like during the RPA Studio install process IONAPI credentials are downloaded from an ION API Authorized App. Can you successfully get a bearer token using the same IONAPI credentials outside of RPA, e.g. in Postman or Hoppscotch?
Yes, works fine with postman.
Hmm, invalid client ID would seem to indicate it's an authentication issue, not authorization, but you could check the permissions on the service user tied to the IONAPI authorized app to confirm it has access to the IMS endpoint, in case the error message doesn't actually reflect the underlying issue. We don't use RPA, so I don't have much other insight into how RPA studio functions.
Have you reviewed the docs in this area: https://docs.infor.com/inforos/2026.x/en-us/useradminlib_cloud/default.html?helpcontent=rpasg/oya1723803026684.html
Other than IMS other ION API requests work fine using the RPA activity. This error is specific to client id used in the IMS connection point , unsure how to override the one that defaults using the RPA activity .
You should be able to use the Client ID of the RPA ION API authorized App in your IMS Connection Point.
If you have other consumers of the IMS connection, you can duplicate the Connection Point with a different Client ID. That way you will also be able to distinguish where a BOD is coming from, RPA or another application.
