ERP automation guide
Prophet 21 Integrations and API Guide
By Airdev. We build custom AI order entry for distributors running Prophet 21: built to match your exact process, owned by you, with no per-order fees. This guide is what we've learned doing it.
Prophet 21 has a serious integration surface: four distinct API layers, all exposed through its middleware server. The two things that surprise teams are that API access is a separately licensed add-on rather than part of the base system, and that the official documentation is thin enough that the working knowledge lives on community forums and in unofficial docs.
This page covers which API to use for what, the licensing catch, where the documentation actually is, what to build first, and who already builds on P21.
The four API surfaces
All four run through the P21 middleware server, and you will see two naming schemes for the same stack. Older documentation talks about the P21 API v2, the Entity API, the Interactive API, and Data Services. The names the community uses map more directly to what each surface is for:
- OData (Data Services in the older docs) handles fast read-only queries against P21 data. Reads belong here, not on the transactional surfaces.
- The Entity API creates and updates master records.
- The Transaction API posts transactions the way a user would, with business rules and screen logic applied. Creating orders and vouchers belongs here.
- The Interactive API drives a real P21 session and can answer the decision points a screen would present. It is the escape hatch for flows that only exist as screens.
The separate API license
The REST API is sold as a separate license: the P21 API asset in your Epicare asset list. Integrations built without it fail with a security exception that reads like a bug, not like a billing problem, and shops routinely discover the license requirement that way. One wrinkle from the field: the legacy SOAP services have worked without the license using the same credentials, which is exactly the kind of inconsistency that convinces people the REST failure is their code. Even experienced community members have gotten P21 licensing wrong, so confirm the API asset is in your contract before anyone writes an integration, and ask about transaction limits while you are at it.
How the Transaction API fails in practice
Because the Transaction API mirrors the screens, its errors often arrive as literal windows. Real examples from the field: automation runs interrupted by an unexpected DynaChange alert window, a surprise email-packing-list prompt breaking an unattended flow, and screens whose tab pages have blank names, which breaks the standard element-addressing convention entirely. None of this is a reason to avoid the API. It is a reason to build integrations with the assumption that P21 will occasionally answer with a window instead of a result, and to handle that instead of crashing the queue.
Where the real documentation lives
Epicor's official API documentation is sparse. The practical sources are the epiusers.help forum, where most integration problems have been hit before even if not always answered, and community-maintained API documentation on GitHub. There is even a market in replacements: SimpleApps sells its own REST API that reads the P21 database directly and powers its e-commerce and mobile apps. Plan for tribal knowledge, not a reference manual.
What to build on it first
The API surface supports plenty (storefront sync, CRM sync, and EDI flows are all common), but the build with the fastest payback at most distributors we talk to is order intake. The orders that arrive as emailed PDFs get keyed by hand into Order Entry, and that re-keying is usually the highest-volume manual work in the building.
The shape of that build: a system reads the emailed PO, matches lines against your item master and customer part number cross references, prices from the account's contract, and stages a draft sales order in P21 through the API. A person reviews the draft and posts it. Everything downstream, from the acknowledgement to fulfillment, runs exactly as if a rep had keyed the order.
The P21 integration ecosystem
You rarely have to start from zero. iPaaS.com maintains a certified P21 connector with prebuilt flows to commerce and CRM platforms. DCKAP Integrator targets distributor e-commerce and CRM sync. BPA Platform handles EDI and TrueCommerce connections. SimpleApps and B2Sell build e-commerce on P21. MindHarbor builds P21-specific apps like purchase order requirements generation imports. For storefront orders, Optimizely's official P21 connector submits order files that P21's Scheduled Import Service Manager picks up.
Order intake automation is its own lane. Conexiom is now an official Epicor partner for P21, Endeavor and OrderPier both advertise P21 integrations, and custom builds like the ones we do round out the field.
Frequently asked questions
Want this for your Prophet 21?
Built around your exact process and your Prophet 21. You own it, with no per-seat or per-order fees.