The API Report CardAPI Index
THE API REPORT CARD / Manufacturing / JobBOSS
JobBOSS

JobBOSS API

Enterprise/HR/ERP · jobboss.com

Integration runs through a downloadable Windows/.NET SDK: a JBRequestProcessor class takes JBXML request envelopes with a SessionID, not a REST API. There is no public developer portal, OAuth, or sandbox; docs ship inside the SDK via ECI's customer portal.

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

SCORECARD

ExistenceGOODA real programmatic surface exists: the downloadable SDK's JBRequestProcessor accepts JBXML query and write envelopes.
AccessPOORSDK and docs are gated through ECI's customer portal and direct contact; no public portal or sandbox tenant to evaluate.
CoveragePOOR
AuthPOORSession-based: acquire a SessionID and embed it in each JBXML envelope; no OAuth, painful for multi-tenant web apps.
Docs & DXPOORDocs ship inside the SDK, a Windows/.NET runtime is required, and reviewers call the XML documentation poor.
StabilityMIXEDReviewers report each update fixes one set of problems and rolls out a new set; upgrades are persistently disruptive.
MORE FROM THE REPORT CARD
Epicor KineticFGlobal Shop SolutionsFCetec ERPD+Accolent ERPD
Supergood: JobBOSS has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

JobBOSS scores D on the API Report Card. Integration runs through a downloadable Windows/.NET SDK: a JBRequestProcessor class takes JBXML request envelopes with a SessionID, not a REST API. There is no public developer portal, OAuth, or sandbox; docs ship inside the SDK via ECI's customer portal.

Tried to integrate with JobBOSS?
SOURCES
"Customer support for using XML extremely limited. Poor documentation on using it.", the JBXML/SDK surface is the primary integration path but is underdocumented capterra.com ↗
SDK requires a Windows / .NET runtime and a JBRequestProcessor COM-style class, not a modern HTTPS REST API, making cross-platform and serverless integrations difficult resource.ecisolutions.com ↗
Session-based authentication (acquire SessionID, embed in JBXML envelope) is not OAuth and is poorly suited to multi-tenant web apps; community forums document concurrency and session-management pain in web-based integration scenarios jobbossuser.com ↗
No public developer portal, no public OpenAPI/Swagger spec, no public sandbox tenant, prospective integrators must engage ECI customer support or sales to evaluate the integration surface ecisolutions.com ↗
QuickBooks integration is the marquee partner connector and is widely reported as broken in production, forcing customers to revert to manual JE entry or pay for custom integration work capterra.com ↗
User-submitted JobBOSS ideas board contains long-open feature requests for modern API surfaces (e.g., "API to send DCMobile transactions directly to JobBoss"), indicating customer demand for first-party REST endpoints that have not yet been delivered ideas.jobboss.com ↗
Third-party unified-API vendors (Makini) and integration consultancies (Commercient, APIWORX-style shops, Sellbery) market themselves explicitly as a workaround for the gated/legacy native surface, a tell that the first-party API is not self-serve makini.io ↗
ECI's PE-backed acquisitive model creates roadmap uncertainty for integrators, JobBOSS, E2, M1, and Deacom are all owned by the same parent and periodically rebundled, which raises switching costs for any integration built against a specific SDK version ecisolutions.com ↗
"Each new update fixes one set of problems but rolls out a new set of problems", upgrades are persistently disruptive capterra.com ↗
Inventory module does not connect to accounting functions, most entries have to be made manually, and reconciling payroll/inventory/accounting is difficult capterra.com ↗
QuickBooks integration is widely reported as broken, multiple reviewers report "could never get the QuickBooks integration to work correctly" after a year+ of trying capterra.com ↗
Customer support has degraded as customers scale, multi-week response times, unresolved tickets, slow escalation on production-impacting issues like inventory errors capterra.com ↗
Software becomes increasingly expensive as the shop grows, per-user/per-seat cost, rising annual maintenance fees, and high cost of migrating to the cloud (JobBOSS²) version getapp.com ↗
Customization and additional support tiers incur significant extra cost on top of the headline license softwaresuggest.com ↗
Reporting customization is limited out-of-the-box; many shops resort to Crystal Reports or Excel pulls against the underlying database capterra.com ↗
ECI Solutions' acquisitive model (Leonard Green-backed PE roll-up of JobBOSS, E2, M1, Deacom, Bolt-On, etc.) means roadmap and pricing are perceived as opaque, with periodic forced upgrades and product-line consolidations trustradius.com ↗
© Supergood Systems, Inc.