Epicor Kinetic
Connect your customers' Epicor Kinetic tenants so your product can read and write business entities through the Kinetic REST API. The customer's basis admin provides a username, password, and CompanyID; Askel composes Basic auth and adds the Company header on every request.
What you can do
Read and create sales orders
Fetch SalesOrder entities with header and line-level detail, or POST new orders with customer, part, quantity, and price data. Covers multi-line orders with different ship-to addresses per line.
Manage the customer master
Read Customer records including name, billing address, credit limit, and payment terms. Create new customers or update addresses when your product's CRM changes need to propagate to Kinetic.
Read part master and inventory data
Fetch Part records with description, unit of measure, product group, and stock quantities by plant and warehouse. Lets your product resolve part numbers without a separate data export.
Read and create purchase orders
Fetch PurchaseOrder entities for procurement-visibility workflows, or create purchase orders in Kinetic from buying events triggered by your product.
Access GL accounts and journal entries
Read the chart of accounts and posted GL transactions for financial workflows that need actual ledger data from the customer's Kinetic environment.
Read job and production order status
Fetch JobHead records for open production jobs, including quantity, scheduling data, and completion percentage. Useful for manufacturing-visibility dashboards in your product.
Pulling open sales orders into a customer-facing order-status portal
You sell an order-transparency platform for manufacturers. A new customer, Belmont Precision Parts, runs Epicor Kinetic as their ERP. Their B2B buyers need a self-service portal to check order status without calling Belmont's inside-sales team. Your product needs to read open sales orders and delivery dates directly from Kinetic.
- 1
Basis admin provides credentials
Belmont's Epicor admin creates a dedicated API service user in Kinetic with read access to the Sales Order and Part entities. They provide your product's connection wizard with the Epicor host URL, the CompanyID (BELMONT), and the service user's username and password.
- 2
Credentials validated
Askel makes a test request to the Kinetic REST API using Basic auth and the Company header. A successful response confirms the credentials and the base URL are correct. The credentials are stored encrypted per customer connection.
- 3
Buyer logs into the portal
When one of Belmont's buyers logs into your order portal, your product calls Askel to fetch all sales orders for that buyer's customer account from Kinetic, filtered by OrderHed.CustNum.
- 4
Order lines and ship dates read
Askel reads the OrderDtl records for each header, returning part number, ordered quantity, shipped quantity, and requested ship date. Your portal displays a line-by-line status table for the buyer.
- 5
Belmont's inside-sales calls reduced
Buyers with order questions resolve them through the portal without calling Belmont's team. Belmont's CS manager tracks the call-volume reduction in your platform's analytics.
Basic auth
The customer's Epicor basis admin provides a service username, password, and CompanyID. Askel base64-encodes the username and password for the Basic auth header and adds the Company header with the CompanyID on every request to the customer's Epicor host. 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 Epicor Kinetic
Does this work for both Epicor Kinetic cloud and on-premises?+
What Epicor security group or permission set does the service user need?+
How does the CompanyID header work in a multi-company Kinetic installation?+
What happens if the service user password changes?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.