authenticate a backend integration to infor ion api using the .ionapi credentials file
domain: developer.infor.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register the integration as an Authorized App in the Infor OS Portal under Admin > Security > Authorized Apps
Download the generated .ionapi file, a JSON document containing the client ID (ci), client secret (cs), tenant id (ti), and the token/authorization/revoke endpoints (ot/oa/or)
For server-to-server calls with no interactive user, use the Resource Owner grant, which additionally requires the service account access key (saak) and secret key (sask) from the same file
Exchange these credentials at the token endpoint (ot) for an access token, then call the ION API Gateway base URL (iu) with it as a bearer token
Refresh or re-request the token before it expires, since access tokens are short-lived
Known gotchas
Infor's Resource Owner grant needs all four of ClientID, ClientSecret, saak, and sask — most generic OAuth2 client libraries only expect a client id/secret pair, so they often need custom parameters
Refresh tokens aren't issued by default and must be explicitly enabled per authorized app; without that, the integration must re-authenticate with the full credential set on every expiry
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?