One API per ERP
Kinetic and Prophet 21: where the agent connects in each Epicor ERP
Epicor Kinetic exposes its services through an Open REST API that follows the OData v4 standard. According to Epicor, anything available in the user interface is available through REST, including business objects, processes, business activity queries (BAQs) and Epicor Functions (Epicor). API keys and access scopes control which services and methods each integration can use, and ERP user and data permissions still apply.
Prophet 21, the Epicor ERP for wholesale distributors, has its own API. The Epicor brochure describes a stateless v2 P21 API, the Entity API with REST endpoints per business object, the Interactive API, which works within a Prophet 21 session, and the Data Services API, which reads the Prophet 21 database over OData; per the same brochure, the API supports REST and SOAP for more than 300 services (Prophet 21 brochure).
That matters in the US market: Enlyft has data on 1,841 companies that use Prophet 21 and finds them most often in the United States, in the wholesale industry and at companies with 50 to 200 employees (Enlyft). At that size, the same few people answer price checks, enter orders and chase deliveries, so every request the agent handles is time back for the team.
To learn about a change, Kinetic runs BPM rules before or after each transaction, and Epicor Functions can call external systems (Epicor Functions). For Prophet 21, we define it during discovery. Epicor also offers Automation Studio, its integration platform powered by Workato, with connectors for Kinetic and Prophet 21 and an on-premises agent that reaches an ERP on your servers without opening ports in the firewall (Automation Studio).
| Surface | What the agent does | What to know |
|---|
| Kinetic REST API | Reads stock and prices, creates quotes and orders | OData v4; API key scoped by service and method |
| BAQs over REST (Kinetic) | Feed Metrix answers | Governed data views, no direct database access |
| BPM and Epicor Functions (Kinetic) | Notify the agent when an order changes | Read-only or read-write, set by the library |
| Prophet 21 API | Looks up items and customers, enters orders | v2 P21 API, Entity API and Interactive API |
| Data Services API (Prophet 21) | Reads for Metrix | OData reads on the database |
Based on Epicor documentation and the Prophet 21 brochure; which surface your project uses depends on your version, your implementation and your contract.
API licensing and terms: what each connection consumes and which modules you need depend on your contract with Epicor. We review it with your team and your Epicor contact before sizing the agent, so nothing surprises you later.