Infor CloudSuite
Connect your customers' Infor CloudSuite tenants so your product can read and write ION API-gated records across financials, HR, and supply chain modules. The customer's admin generates a Service Account in Infor OS and uploads the .ionapi file; Askel uses it to mint short-lived bearer tokens per request.
What you can do
Read financial transactions and journal entries
Fetch journal entries, AP invoices, and AR transactions from the customer's CloudSuite Financials environment through ION API endpoints, for reconciliation or reporting workflows in your product.
Manage customers and suppliers
Read and update customer and supplier master records including name, address, payment terms, and tax classification across the customer's CloudSuite environment.
Read inventory and item master data
Fetch item records with unit of measure, product group, and on-hand quantities by location. Lets your product resolve item codes without a separate extract.
Access purchase orders and receipts
Read purchase order headers and lines, including requested and promised dates and receipt quantities, for procurement-visibility workflows running in your product.
Read HR and workforce data
Fetch employee records, position assignments, and department hierarchies from CloudSuite HCM for onboarding and access-provisioning workflows.
Post ION API outbound documents
Send BOD (Business Object Document) payloads back into the Infor ION message bus for integration patterns where your product needs to trigger downstream CloudSuite workflows.
Pulling accounts-payable invoice data into a spend-analytics platform
You sell a spend-analytics platform. A new customer, Crestline Distribution Holdings, manages their financials in Infor CloudSuite Financials. Their CFO wants to see supplier spend by category and payment aging inside your platform without exporting CSVs from CloudSuite each month.
- 1
Admin generates a Service Account
Crestline's IT admin opens Infor OS Portal and navigates to IFS Authorized Apps. They create a new authorised application for your platform, grant it access to the Financials API scope, and generate a Service Account. They download the resulting .ionapi JSON bundle.
- 2
File uploaded to Askel
Crestline's admin uploads the .ionapi file to your product's connection wizard. Askel parses the bundle, extracts the token endpoint, client credentials, and the ION API base URL, and stores them encrypted per customer connection.
- 3
Token minted on first call
Askel makes a client_credentials token request to Crestline's ION token endpoint using the credentials from the .ionapi file. The token is used for the API call and then discarded; a fresh token is minted per request.
- 4
AP invoice data fetched
Askel calls the ION API AP invoice endpoint for Crestline's tenant. Your platform receives invoice headers with supplier, invoice date, amount, and payment status. The data is loaded into your spend-analytics engine.
- 5
Monthly refresh automated
Your platform refreshes the AP data on a nightly schedule via Askel. Crestline's CFO opens the spend dashboard each morning with fresh data from CloudSuite, without any manual export or email.
Service account
The customer's admin generates a Service Account in Infor OS Portal under IFS Authorized Apps and uploads the resulting .ionapi JSON file to Askel. The file contains the ION token URL, client ID, client secret, and the ION API base URL. Askel uses the client credentials to mint short-lived bearer tokens per request. The .ionapi file is stored encrypted in Askel and never forwarded to your servers.
How Askel sits between your product and the customer's system
FAQ for Infor CloudSuite
Does this work for all CloudSuite applications (Financials, HCM, Distribution, etc.)?+
What is an .ionapi file and is it safe to upload?+
What if the customer regenerates the Service Account credentials?+
How is the ION API different from direct CloudSuite application APIs?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.