IFS Cloud
Connect your customers' IFS Cloud tenants so your product can read and write OData entities across manufacturing, service, and project modules. The customer's IFS admin registers an OAuth client in IFS IAM (Keycloak); Askel mints client_credentials tokens against the realm token URL per request.
What you can do
Read work orders and service jobs
Fetch work order headers and lines with equipment reference, reported fault, planned start date, and completion status. Useful for field-service visibility platforms that need live job data from IFS.
Read and create customer orders
Fetch open customer orders with line-level detail, or POST new orders with customer, part number, quantity, and wanted delivery date into the customer's IFS tenant.
Access parts and inventory
Read part catalog records with descriptions, unit of measure, and on-hand quantities by site. Lets your product resolve IFS part numbers without a separate export.
Read project and activity data
Fetch project headers, activities, and resource bookings for project-management visibility workflows that surface IFS project state in your platform.
Read supplier and purchase orders
Fetch supplier records and purchase order data for procurement-tracking workflows that need live data from the customer's IFS procurement module.
Access financial and cost accounting data
Read vouchers, cost centres, and account balances for financial consolidation or reporting workflows that require actual posted figures from IFS Cloud.
Displaying live field-service job status in a customer self-service portal
You sell a customer self-service portal for industrial equipment companies. A new customer, Pemberton Service Solutions, manages all their field-service work orders in IFS Cloud. Their end-customers want to see real-time job progress, technician assigned, and estimated completion date without calling Pemberton's service desk.
- 1
IFS admin registers an OAuth client
Pemberton's IFS administrator opens IFS IAM (Keycloak) in their IFS Cloud tenant, navigates to the correct realm, creates a new client with the client_credentials grant type, and notes the client ID and client secret. They provide your portal's connection wizard with the IFS host URL, realm name, client ID, and client secret.
- 2
Connection validated
Askel makes a client_credentials token request to Pemberton's IFS IAM realm token endpoint. On success, it uses the token to make a test OData request to the WorkOrder entity endpoint and confirms read access.
- 3
Buyer company mapping
Askel reads the Customer entity from Pemberton's IFS tenant. Your portal maps each of Pemberton's end-customers to their IFS customer ID so that job lookups can be scoped per customer.
- 4
Work orders fetched per portal session
When an end-customer logs into the portal, your product calls Askel to fetch open work orders for their IFS customer ID. Askel reads the WorkOrder OData endpoint filtered by CustomerNo and returns job status, technician, and estimated completion date.
- 5
Portal status updated
The end-customer sees a live list of open and recently completed jobs with status descriptions sourced directly from IFS. Pemberton's service desk volume drops because customers find status information themselves.
Service account
The customer's IFS admin registers an OAuth client in IFS IAM (Keycloak) with the client_credentials grant type and provides Askel with the client ID, client secret, IFS Cloud host URL, and the Keycloak realm name. Askel constructs the realm token URL and mints a short-lived bearer token per request. Credentials are stored encrypted per connection and never forwarded to your servers.
How Askel sits between your product and the customer's system
FAQ for IFS Cloud
Does this work for IFS Cloud 21R2 and later versions?+
What is an IFS IAM realm and how does the customer find it?+
Can we scope the OAuth client to specific IFS modules?+
What if the customer is hosted by IFS on their cloud infrastructure?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.