Accounting · Beta
Epicor Kinetic
API integration
Ship Accounting features without building the integration. Full Epicor Kinetic API access via Proxy and 70+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Epicor Kinetic
Common scenarios for SaaS companies building Epicor Kinetic integrations for their customers.
Embed AP automation into Epicor Kinetic customers' AP workflows
Spend management and AP automation platforms can sync vendors, purchase orders, and PO lines from Epicor Kinetic for 3-way matching, then push approved payables back as AP invoices without their customers writing a line of integration code.
Power B2B commerce and CPQ with live ERP data
E-commerce, CPQ, and quoting platforms can pull real-time Epicor Kinetic parts, customers, and pricing to display accurate catalogs, then create sales orders, sales order lines, and quotes directly in the ERP upon checkout.
Connect shop floor and field service apps to manufacturing jobs
MES, maintenance, and field service SaaS can read active jobs, employees, and parts from Epicor Kinetic, then use Epicor Functions to safely log labor and material consumption without violating Kinetic's job-costing rules.
Feed BI and analytics dashboards with pre-joined ERP data
Analytics platforms can let end users pick an existing Business Activity Query (BAQ) in their Epicor Kinetic tenant and stream the results through Truto, avoiding thousands of fragmented OData calls to assemble financial or operational views.
Sync CRM customers and contacts bi-directionally with Epicor
CRM and customer success tools can keep Epicor Kinetic customers and customer contacts in sync so sales reps always work from the ERP's source-of-truth account data, including credit status and shipping details.
What You Can Build
Ship these features with Truto + Epicor Kinetic
Concrete product features your team can ship faster by leveraging Truto’s Epicor Kinetic integration instead of building from scratch.
Vendor and PO sync with AP invoice write-back
Pull vendors, purchase orders, and PO lines on a schedule and create AP invoices in Epicor Kinetic once invoices are approved in your product.
Sales order and quote creation from external carts
Create and update Epicor Kinetic quotes, quote lines, sales orders, and sales order lines directly from your checkout, CPQ, or quoting flow.
Parts and inventory catalog mirroring
List, fetch, and update Epicor Kinetic parts across sites to power product catalogs, availability lookups, and item master synchronization.
Customer shipment tracking surface
Expose customer shipments inside your logistics or portal UI by listing and retrieving shipment records and updating them as status changes occur.
BAQ-powered custom reporting connector
Let your users select from their own Epicor BAQs and stream results into dashboards, exports, or warehouses without building custom endpoints per customer.
Epicor Functions trigger for shop floor transactions
Invoke customer-defined Epicor Functions and Business Object methods to run complex multi-step logic — like clocking labor into a job and consuming parts — from your app.
SuperAI
Epicor Kinetic AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_epicor_kinetic_ap_invoices
List AP invoices (Erp.BO.APInvoiceSvc/APInvoices). Filter with OData `filter` (e.g. `InvoiceNum eq ...`); the connector pages through all results, 100 per page. Required: vendor_num. Lists lines across all parents; filter by parent, e.g. `VendorNum eq 5000`.
get_single_epicor_kinetic_ap_invoice_by_id
Get one AP invoice by its key (Erp.BO.APInvoiceSvc/APInvoices). Required: vendor_num, id.
create_a_epicor_kinetic_ap_invoice
Create a AP invoice (POST Erp.BO.APInvoiceSvc/APInvoices). Send the APInvHed columns to set; Epicor fills defaults and the system-assigned key. Required: vendor_num.
update_a_epicor_kinetic_ap_invoice_by_id
Update a AP invoice (PATCH Erp.BO.APInvoiceSvc/APInvoices): send only the columns to change. Epicor answers 204 with an empty body. Required: vendor_num, id.
delete_a_epicor_kinetic_ap_invoice_by_id
Delete a AP invoice (DELETE Erp.BO.APInvoiceSvc/APInvoices). Epicor answers 204; records with dependent data cannot be deleted. Required: vendor_num, id.
list_all_epicor_kinetic_ar_invoices
List AR invoices (Erp.BO.ARInvoiceSvc/ARInvoices). Filter with OData `filter` (e.g. `CustNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_ar_invoice_by_id
Get one AR invoice by its key (Erp.BO.ARInvoiceSvc/ARInvoices). Required: id.
create_a_epicor_kinetic_ar_invoice
Create a AR invoice (POST Erp.BO.ARInvoiceSvc/ARInvoices). Send the InvcHead columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_ar_invoice_by_id
Update a AR invoice (PATCH Erp.BO.ARInvoiceSvc/ARInvoices): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_ar_invoice_by_id
Delete a AR invoice (DELETE Erp.BO.ARInvoiceSvc/ARInvoices). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_baq_results
Run a BAQ and return its rows (GET BaqSvc/
list_all_epicor_kinetic_baqs
List the BAQs (Business Activity Queries) the connected user can run through REST (the BaqSvc service document). Use a BAQ's name as `baq_id` in baq_results.list.
epicor_kinetic_business_object_methods_execute
Call any business object method (POST /api/v2/odata/
list_all_epicor_kinetic_customer_contacts
List customer contacts (Erp.BO.CustCntSvc/CustCnts). Filter with OData `filter`, e.g. `CustNum eq 12`; the connector pages through all results, 100 per page.
create_a_epicor_kinetic_customer_contact
Create a customer contact (POST Erp.BO.CustCntSvc/CustCnts). Send the CustCnt columns to set; Epicor fills defaults and the system-assigned key.
list_all_epicor_kinetic_customer_shipments
List customer shipments (Erp.BO.CustShipSvc/CustShips). Filter with OData `filter` (e.g. `CustNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_customer_shipment_by_id
Get one customer shipment by its key (Erp.BO.CustShipSvc/CustShips). Required: id.
update_a_epicor_kinetic_customer_shipment_by_id
Update a customer shipment (PATCH Erp.BO.CustShipSvc/CustShips): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
list_all_epicor_kinetic_customers
List customers (Erp.BO.CustomerSvc/Customers). Filter with OData `filter` (e.g. `CustID eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_customer_by_id
Get one customer by its key (Erp.BO.CustomerSvc/Customers). Required: id.
create_a_epicor_kinetic_customer
Create a customer (POST Erp.BO.CustomerSvc/Customers). Send the Customer columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_customer_by_id
Update a customer (PATCH Erp.BO.CustomerSvc/Customers): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_customer_by_id
Delete a customer (DELETE Erp.BO.CustomerSvc/Customers). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_employees
List employees (Erp.BO.EmpBasicSvc/EmpBasics). Filter with OData `filter` (e.g. `Name eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_employee_by_id
Get one employee by its key (Erp.BO.EmpBasicSvc/EmpBasics). Required: id.
create_a_epicor_kinetic_employee
Create a employee (POST Erp.BO.EmpBasicSvc/EmpBasics). Send the EmpBasic columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_employee_by_id
Update a employee (PATCH Erp.BO.EmpBasicSvc/EmpBasics): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_employee_by_id
Delete a employee (DELETE Erp.BO.EmpBasicSvc/EmpBasics). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
epicor_kinetic_functions_execute
Run an Epicor Function (POST /api/v2/efx/
list_all_epicor_kinetic_jobs
List jobs (Erp.BO.JobEntrySvc/JobEntries). Filter with OData `filter` (e.g. `PartNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_job_by_id
Get one job by its key (Erp.BO.JobEntrySvc/JobEntries). Required: id.
create_a_epicor_kinetic_job
Create a job (POST Erp.BO.JobEntrySvc/JobEntries). Send the JobHead columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_job_by_id
Update a job (PATCH Erp.BO.JobEntrySvc/JobEntries): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_job_by_id
Delete a job (DELETE Erp.BO.JobEntrySvc/JobEntries). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
create_a_epicor_kinetic_login_token
Log in as the connected Epicor user and return a bearer token (POST TokenResource.svc). The connector calls this on connect and every 20 minutes; you rarely need it directly.
list_all_epicor_kinetic_parts
List parts (Erp.BO.PartSvc/Parts). Filter with OData `filter` (e.g. `PartDescription eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_part_by_id
Get one part by its key (Erp.BO.PartSvc/Parts). Required: id.
create_a_epicor_kinetic_part
Create a part (POST Erp.BO.PartSvc/Parts). Send the Part columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_part_by_id
Update a part (PATCH Erp.BO.PartSvc/Parts): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_part_by_id
Delete a part (DELETE Erp.BO.PartSvc/Parts). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_purchase_order_lines
List purchase order lines (Erp.BO.POSvc/PODetails). Filter with OData `filter` (e.g. `POLine eq ...`); the connector pages through all results, 100 per page. Required: po_num. Lists lines across all parents; filter by parent, e.g. `PONUM eq 5000`.
get_single_epicor_kinetic_purchase_order_line_by_id
Get one purchase order line by its key (Erp.BO.POSvc/PODetails). Required: po_num, id.
create_a_epicor_kinetic_purchase_order_line
Create a purchase order line (POST Erp.BO.POSvc/PODetails). Send the PODetail columns to set; Epicor fills defaults and the system-assigned key. Required: po_num.
update_a_epicor_kinetic_purchase_order_line_by_id
Update a purchase order line (PATCH Erp.BO.POSvc/PODetails): send only the columns to change. Epicor answers 204 with an empty body. Required: po_num, id.
delete_a_epicor_kinetic_purchase_order_line_by_id
Delete a purchase order line (DELETE Erp.BO.POSvc/PODetails). Epicor answers 204; records with dependent data cannot be deleted. Required: po_num, id.
list_all_epicor_kinetic_purchase_orders
List purchase orders (Erp.BO.POSvc/POes). Filter with OData `filter` (e.g. `VendorNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_purchase_order_by_id
Get one purchase order by its key (Erp.BO.POSvc/POes). Required: id.
create_a_epicor_kinetic_purchase_order
Create a purchase order (POST Erp.BO.POSvc/POes). Send the POHeader columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_purchase_order_by_id
Update a purchase order (PATCH Erp.BO.POSvc/POes): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_purchase_order_by_id
Delete a purchase order (DELETE Erp.BO.POSvc/POes). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_quote_lines
List quote lines (Erp.BO.QuoteSvc/QuoteDtls). Filter with OData `filter` (e.g. `QuoteLine eq ...`); the connector pages through all results, 100 per page. Required: quote_num. Lists lines across all parents; filter by parent, e.g. `QuoteNum eq 5000`.
get_single_epicor_kinetic_quote_line_by_id
Get one quote line by its key (Erp.BO.QuoteSvc/QuoteDtls). Required: quote_num, id.
create_a_epicor_kinetic_quote_line
Create a quote line (POST Erp.BO.QuoteSvc/QuoteDtls). Send the QuoteDtl columns to set; Epicor fills defaults and the system-assigned key. Required: quote_num.
update_a_epicor_kinetic_quote_line_by_id
Update a quote line (PATCH Erp.BO.QuoteSvc/QuoteDtls): send only the columns to change. Epicor answers 204 with an empty body. Required: quote_num, id.
delete_a_epicor_kinetic_quote_line_by_id
Delete a quote line (DELETE Erp.BO.QuoteSvc/QuoteDtls). Epicor answers 204; records with dependent data cannot be deleted. Required: quote_num, id.
list_all_epicor_kinetic_quotes
List quotes (Erp.BO.QuoteSvc/Quotes). Filter with OData `filter` (e.g. `CustNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_quote_by_id
Get one quote by its key (Erp.BO.QuoteSvc/Quotes). Required: id.
create_a_epicor_kinetic_quote
Create a quote (POST Erp.BO.QuoteSvc/Quotes). Send the QuoteHed columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_quote_by_id
Update a quote (PATCH Erp.BO.QuoteSvc/Quotes): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_quote_by_id
Delete a quote (DELETE Erp.BO.QuoteSvc/Quotes). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_sales_order_lines
List sales order lines (Erp.BO.SalesOrderSvc/OrderDtls). Filter with OData `filter` (e.g. `OrderLine eq ...`); the connector pages through all results, 100 per page. Required: order_num. Lists lines across all parents; filter by parent, e.g. `OrderNum eq 5000`.
get_single_epicor_kinetic_sales_order_line_by_id
Get one sales order line by its key (Erp.BO.SalesOrderSvc/OrderDtls). Required: order_num, id.
create_a_epicor_kinetic_sales_order_line
Create a sales order line (POST Erp.BO.SalesOrderSvc/OrderDtls). Send the OrderDtl columns to set; Epicor fills defaults and the system-assigned key. Required: order_num.
update_a_epicor_kinetic_sales_order_line_by_id
Update a sales order line (PATCH Erp.BO.SalesOrderSvc/OrderDtls): send only the columns to change. Epicor answers 204 with an empty body. Required: order_num, id.
delete_a_epicor_kinetic_sales_order_line_by_id
Delete a sales order line (DELETE Erp.BO.SalesOrderSvc/OrderDtls). Epicor answers 204; records with dependent data cannot be deleted. Required: order_num, id.
list_all_epicor_kinetic_sales_orders
List sales orders (Erp.BO.SalesOrderSvc/SalesOrders). Filter with OData `filter` (e.g. `CustNum eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_sales_order_by_id
Get one sales order by its key (Erp.BO.SalesOrderSvc/SalesOrders). Required: id.
create_a_epicor_kinetic_sales_order
Create a sales order (POST Erp.BO.SalesOrderSvc/SalesOrders). Send the OrderHed columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_sales_order_by_id
Update a sales order (PATCH Erp.BO.SalesOrderSvc/SalesOrders): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_sales_order_by_id
Delete a sales order (DELETE Erp.BO.SalesOrderSvc/SalesOrders). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
list_all_epicor_kinetic_sites
List sites (Erp.BO.PlantSvc/Plants). Filter with OData `filter` (e.g. `Name eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_site_by_id
Get one site by its key (Erp.BO.PlantSvc/Plants). Required: id.
list_all_epicor_kinetic_vendors
List suppliers (Erp.BO.VendorSvc/Vendors). Filter with OData `filter` (e.g. `VendorID eq ...`); the connector pages through all results, 100 per page.
get_single_epicor_kinetic_vendor_by_id
Get one supplier by its key (Erp.BO.VendorSvc/Vendors). Required: id.
create_a_epicor_kinetic_vendor
Create a supplier (POST Erp.BO.VendorSvc/Vendors). Send the Vendor columns to set; Epicor fills defaults and the system-assigned key.
update_a_epicor_kinetic_vendor_by_id
Update a supplier (PATCH Erp.BO.VendorSvc/Vendors): send only the columns to change. Epicor answers 204 with an empty body. Required: id.
delete_a_epicor_kinetic_vendor_by_id
Delete a supplier (DELETE Erp.BO.VendorSvc/Vendors). Epicor answers 204; records with dependent data cannot be deleted. Required: id.
Why Truto
Why use Truto’s MCP server for Epicor Kinetic
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1100+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Start with Epicor Kinetic in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s Epicor Kinetic account
Use Truto’s frontend SDK to connect your customer’s Epicor Kinetic account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Epicor Kinetic
Truto’s Proxy API is a 1-to-1 mapping of the Epicor Kinetic API. You call us, we call Epicor Kinetic, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Epicor Kinetic’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Epicor Kinetic on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication to Epicor Kinetic work for our end users?
Truto handles the Epicor Kinetic auth flow, including generating a login token via the create_a_epicor_kinetic_login_token endpoint and managing session credentials. Your users connect their Kinetic tenant through Truto's Link UI or API, and Truto stores and refreshes credentials so you never touch them.
Does Truto support both cloud and on-premise Epicor Kinetic deployments?
Yes. Epicor Kinetic is deployed both as Epicor-hosted cloud and customer on-premise installations. Truto can connect to either, as long as the Kinetic REST/OData API endpoint is reachable from Truto — on-prem customers typically expose their Kinetic server endpoint during the connection step.
How do we handle Epicor's stateful Business Object model when creating records?
Simple POSTs to Kinetic often fail because Business Objects require initialization methods (e.g. GetNewOrderHed) before data can be patched. Truto exposes epicor_kinetic_business_object_methods_execute so you can invoke those native methods and then follow up with the standard create/update calls — matching how the Kinetic UI itself writes data.
Can we query custom joined data or run reports that span multiple tables?
Yes. Use list_all_epicor_kinetic_baqs to enumerate the Business Activity Queries defined in your customer's tenant, then call list_all_epicor_kinetic_baq_results to stream pre-joined, pre-calculated rows. This is the recommended pattern for analytics and reporting workloads instead of stitching OData calls together.
What core objects can we read and write today?
Truto exposes full CRUD on customers, vendors, parts, employees, jobs, quotes and quote lines, sales orders and sales order lines, purchase orders and PO lines, AP invoices, and AR invoices. Customer contacts, customer shipments, and sites are also available, along with BAQ, Business Object, and Function execution endpoints.
How does Truto handle pagination and rate limits on Kinetic's API?
Truto normalizes Kinetic's OData pagination behind cursor-based responses on all list_all_* endpoints, so you iterate consistently without managing $skip/$top yourself. Requests are throttled to stay within each tenant's limits, and Truto automatically retries transient failures.
Can we trigger customer-specific business logic that an Epicor admin has built?
Yes. If your customer's Epicor administrator has published Epicor Functions (custom C# server-side logic), you can invoke them through epicor_kinetic_functions_execute. This is the safest way to run multi-step transactions like job labor posting without violating Kinetic's internal costing rules.
Epicor Kinetic
Get Epicor Kinetic integrated into your app
Our team understands what it takes to make a Epicor Kinetic integration successful. A short, crisp 30 minute call with folks who understand the problem.