Reference · built on requestConnectorERP & finance

Epicor Kinetic

Business objects, Business Activity Queries, reports, and Epicor Functions from Epicor Kinetic over its OData v4 REST services.

Request accessPricing ↗

About

Epicor Kinetic is Epicor's manufacturing ERP. Its Open REST API exposes the same services the Kinetic user interface uses: business objects, processes, reports, Business Activity Queries (BAQs), and Epicor Functions, as versioned OData v4 services with metadata discovery. Each installation carries interactive REST help for browsing services, inspecting metadata, and testing calls. Access is controlled with API keys, access scopes, and the existing ERP user and data permissions.

An operator on Fibric reads orders, jobs, and inventory through the business objects and BAQs you expose, and proposes an update or a function run for your approval. A receipt follows every proposal, with what changed, why, and the undo step.

This is a reference listing. It documents what Fibric would read from Epicor Kinetic and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Business objects and their methods, as versioned REST services mirroring the Kinetic service architecture
  • Business Activity Query (BAQ) result sets over OData v4, with query parameters and $metadata
  • Reports and processes exposed as services
  • Return values from Epicor Functions, with data access set read-only or read-write at the library level
  • Service and method metadata from the built-in interactive REST help

Proposed actions

  • Target capability: propose an update to a business object through its REST service method
  • Target capability: propose running an Epicor Function exposed through REST, with its inputs shown for review

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reprioritize the shop-floor backlog

    Read open jobs and material availability through BAQs and propose a revised sequence for the planner to approve.

    With Backlog Priority, Changeover Plan

  • Reorder parts before a line stops

    Compare on-hand and allocated quantities from a BAQ with upcoming job demand and draft the purchase suggestion.

    With Parts Reorder, Reorder Point

  • Run a function only when a person says go

    Show the inputs of an Epicor Function, such as a price update, and run it once approved, with the result logged.

    With Price List Drift, Discount Approval

Requirements

  • An Epicor Kinetic deployment with REST services enabled and reachable over HTTPS
  • An API key created for the integration and scoped to the services it needs
  • An ERP user whose data permissions match what the operator should see
  • BAQs or Epicor Function libraries built inside Kinetic for any query or logic beyond the standard services
Authentication
An API key with access scopes that limit which services and methods the integration may call, combined with the ERP user's own permissions.

Limits

  • Epicor's public pages document no rate limits; this listing makes no throughput claim
  • Detailed service and method references sit inside each installation's REST help, not on a public site
  • Custom C# code inside Epicor Functions can be written only by authorized users under library-level security
  • Access scopes decide which services and methods an API key can reach; services outside the scope are unavailable to it

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Epicor Kinetic ↗

Questions and answers

Is the Kinetic REST API OData?
Yes. Epicor states that its REST services follow the OData v4 standard, which enables query parameters, metadata discovery, and use from OData-aware tools such as Excel and Power BI.
Can custom logic be called from outside Kinetic?
Yes. Epicor Functions are exposed directly through REST and can be invoked internally or externally. Functions sit in libraries with role-based security, ownership controls, and versioning.
How is API access controlled?
With API keys, access scopes, and standard authentication methods. Epicor says security aligns with existing ERP user and data permissions, so an integration sees only what its user may see.
Ask about Epicor Kinetic

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Epicor Kinetic through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy