The API Report CardAPI Index
E2 Shop System

E2 Shop System API

ecisolutions.com

JobBOSS2 (E2) has a real API and SDK, but everything lives behind ECI's gated customer portal. There is no public endpoint reference, OpenAPI spec, sandbox, or documented auth flow; third party platforms like Makini exist mainly to wrap the surface for customers.

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

SCORECARD

ExistenceGOODA JobBOSS2 API and Software Developers' Kit exist, distributed through ECI's customer portal.
AccessPOORDocs and SDK sit behind the ECI customer portal; integrators cannot evaluate the surface without a customer relationship.
CoveragePOORNo public endpoint catalog; real time sync happens via polling or flat file batch rather than webhooks.
AuthPOORNo published OAuth or key flow; integrators discover authentication empirically through the SDK or partner channels.
Docs & DXPOORNo public API reference, OpenAPI spec, sandbox, or webhook catalog; documentation requires a customer portal login.
StabilityMIXED
Supergood: E2 Shop System has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

E2 Shop System scores D on the API Report Card. JobBOSS2 (E2) has a real API and SDK, but everything lives behind ECI's gated customer portal. There is no public endpoint reference, OpenAPI spec, sandbox, or documented auth flow; third party platforms like Makini exist mainly to wrap the surface for customers.

Tried to integrate with E2 Shop System?
SOURCES
No public, self-serve developer portal, API documentation lives behind the ECI customer portal (resource.ecisolutions.com / customerportal.ecisolutions.com), so prospective integrators and ISVs cannot evaluate the API surface without an active JobBOSS2 customer relationship resource.ecisolutions.com β†—
No published OpenAPI/Swagger spec, no public endpoint reference, no documented rate limits, no public sandbox, third-party integration vendors (Makini, Sellbery) explicitly position their products as wrappers because customers cannot easily integrate themselves makini.io β†—
QuickBooks integration is one of the most heavily marketed connectors but is repeatedly reported as broken or requiring expensive professional services, Capterra reviews describe paying ECI's onsite trainer $1200/day without successfully completing a QuickBooks data download capterra.com β†—
Paperless Parts integration (a primary quoting front-end for thousands of machine shops) does not always sync cleanly with JobBOSS2 / E2, listed publicly as an integration partner, but customers report data points failing to transfer end-to-end paperlessparts.com β†—
Authentication model is not publicly documented, ECI marketing references 'encryption protocols alongside access control features' without a published OAuth/key flow, so integrators discover auth empirically through the SDK or partner channels ecisolutions.com β†—
Webhook / event-stream surface is not publicly documented; real-time sync to CRMs, BI, and e-commerce platforms is achieved primarily through polling or flat-file batch, which is brittle at scale makini.io β†—
A cottage industry of paid third-party connectors (Makini, Sellbery, JobBOSS2 SYNC for Salesforce, KnowledgeSync ITC, CADLink, Alora) exists primarily to abstract the JobBOSS API, each layer adds subscription cost and a second vendor between the customer and their own data appexchange.salesforce.com β†—
Customers on legacy on-premise E2 SHOP installs face additional friction exposing the API to outside SaaS integrations, networking, VPN, and firewall changes must be coordinated with the shop's IT, slowing or blocking many integrations resource.ecisolutions.com β†—
The forced migration path from legacy E2 SHOP to JobBOSS2 has changed underlying schemas and integration surfaces, requiring integrators to re-certify connectors and customers to redo flat-file/QuickBooks mappings capterra.com β†—
There is no public developer community (no GitHub SDK org, no Stack Overflow tag of any meaningful size, no developer Discord/forum), practical integration knowledge is concentrated inside ECI Professional Services and a handful of paid partners sellbery.com β†—
Reviewers describe poor UX ("poor programming from 1985"), with simple actions like printing a work router requiring '10 clicks in and 10 clicks out' practicalmachinist.com β†—
Forced upgrades from legacy E2 to JobBOSS2 have caused 'computer glitches, accounting problems, data loss and production interruption due to malfunctioning software' for at least one shop capterra.com β†—
QuickBooks integration is widely reported as broken or fragile, one customer 'flew in their 1:1 trainer at $1200 per day, and even he could not get the QuickBooks integration to download correctly' capterra.com β†—
Accounting features are described as lacking, no drill-down, multi-step workarounds for tasks that should be simple, sometimes taking 30+ minutes capterra.com β†—
Web app is finicky and intermittently logs users out without warning; inventory module is not intuitive g2.com β†—
TCO is high, significant initial license cost, costly maintenance fees, expensive additional user licenses, with customization and support often metered separately itqlick.com β†—
Shipping integration is partial, does not integrate well with UPS, only commercial invoices available for Canada capterra.com β†—
Paperless Parts (a primary quoting front-end for many shops) does not always sync cleanly with E2/JobBOSS2, data points reportedly fail to transfer end-to-end paperlessparts.com β†—
Several reviewers warn 'BUYER BEWARE' citing poor support response on non-premium tiers and limited recourse after the JobBOSS2 forced migration softwareadvice.com β†—