The API Report CardAPI Index
Deacom

Deacom API

Process Manufacturing ERP (Batch / Formula) · deacom.com

Deacom ships a REST and JSON CRUD API surfaced through a Swagger UI on each customer site, using ECI-issued client credentials for 15 minute bearer tokens. There is no self-serve signup, sandbox, or public pricing, and most third-party integrations are sold as fixed-fee services.

Last verified: July 2026Manufacturing
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA REST and JSON CRUD API ships with every install, surfaced through Swagger UI with row_version fields for delta loads.
AccessPOORCredentials are ECI-issued with no self-serve signup, sandbox, or public pricing; most integrations are sold engagements.
CoveragePOORThe API is raw CRUD over Deacom tables; integrators must learn the database schema to create valid records.
AuthGOODOAuth-style client_id and client_secret exchange for bearer tokens; expiry is short at about 15 minutes.
Docs & DXPOORSwagger UI lives on each customer site only; docs assume knowledge of Deacom's tables, with training hours sold to fill gaps.
StabilityMIXEDrow_version fields enable clean delta syncs, but the API runs as an on-prem Windows service ECI operates for hosted tenants.
Supergood: Deacom has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Deacom scores D on the API Report Card. Deacom ships a REST and JSON CRUD API surfaced through a Swagger UI on each customer site, using ECI-issued client credentials for 15 minute bearer tokens. There is no self-serve signup, sandbox, or public pricing, and most third-party integrations are sold as fixed-fee services.

Tried to integrate with Deacom?
SOURCES
Public API access is gated behind ECI-issued client_id / client_secret credentials with no self-serve developer signup, no public sandbox tenant, and no openly published pricing helptest.deacom.com
The Public API runs as an on-prem 'Windows service' ('Deacom Service: Deacom API'), so integrators of cloud-hosted customers depend on ECI to expose and operate the service rather than hitting a managed multi-tenant endpoint helptest.deacom.com
Bearer access tokens are valid for only ~15 minutes, requiring every integration to manage frequent token refresh against ECI-issued secrets helptest.deacom.com
Deacom explicitly positions integrations as a fixed-fee Professional Services line through the 'Deacom Integration Team' for anything outside the small set of built-in connectors (FedEx/UPS/EasyPost/Avatax/TaxJar/currency/scales), meaning most third-party data extraction is a sold engagement, not a self-serve API call ecisolutions.com
Developers must learn the Deacom database directly, official docs state required knowledge includes 'Tables relationships' and 'What is needed to create a valid record in Deacom', pushing complexity onto the integrator and effectively requiring training hours from ECI helptest.deacom.com
Reviewer complaints about 'limited support for macros and scripts' and 'many tasks done manually that could be automated' suggest the in-app scripting/automation layer is materially thinner than its marketing implies g2.com
Getting reporting and analytical data out of Deacom is widely flagged as difficult ('Getting information out of Deacom in a pretty report form can be difficult'), pushing customers toward external BI extraction that the platform does not natively make easy g2.com
No public GitHub presence, no public client libraries, no public Postman collection, no public rate-limit documentation, and the Swagger docs live on the customer's own Deacom instance rather than a stable developer portal helptest.deacom.com
'Our integration scope is much smaller than other vendors, and limited to communicating with systems that are firmly outside of our ERP Fence', ECI's own positioning frames the API surface as deliberately narrow, which discourages an open ecosystem of third-party data products ecisolutions.com
EDI and trading-partner data flows are handled inside Deacom rather than through an open standards-based partner ecosystem, so external apps wanting EDI-derived data still depend on Deacom's database and Public API gates ecisolutions.com
'Not intuitive, crashed regularly, lost data', multiple reviewers report stability and data-loss issues, with 'most plant employees hating it' g2.com
UI is window-heavy and unintuitive: 'generates a ton of windows instead of having a single, integrated UI' and 'It takes a lot of clicks to get where I want to go' capterra.com
'Everyone that used it felt punished', described as not user-friendly, with a lot of trial-and-error required to learn the system capterra.com
Reporting is hard to extract: 'Getting information out of Deacom in a pretty report form can be difficult' g2.com
Limited automation and scripting: organizations report 'problems with automation and limited support for macros and scripts, with many tasks done manually that could be automated' g2.com
Implementation team turnover and disorganization: 'The implementation team fluctuated and was disorganized' and 'The product felt like it was in Beta and changed constantly' capterra.com
CRM module usability is weak: 'CRM useability is not easy; it takes too many steps' capterra.com
Cultural/support complaint: 'Not only is the software unintuitive the people are condescending' capterra.com
Pricing is opaque: published estimates put TCO between $50K and $800K with $100–$200/user/month, but Deacom does not publish list prices and customers must engage sales for any quote erpresearch.com
Capterra overall rating sits at 3.7/5, well below tier-1 cloud ERPs, signaling persistent satisfaction gaps despite a loyal subset of customers capterra.com