Determine whether JobBOSS2 (ECI) exposes a public, self-service API a shop can integrate against without vendor involvement
domain: fab shop software integration honest-negative · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check ECI's integrations portal at integrations.ecimanufacturing.com, which documents a product-agnostic API covering Deacom, M1, Macola, and JobBOSS2
Confirm JobBOSS2's own API is currently limited to JobBOSS2 hosted/Cloud customers, not on-premise installations
Note that APIs must be activated by ECI before use — this is not a self-serve signup; a shop must contact their ECI account manager or support to enable it
Check the JobBOSS SDK resource page (resource.ecisolutions.com) for the older desktop-integration SDK if the shop is on an on-premise install rather than Cloud
Report to the shop that there is no fully open/public OpenAPI spec they can browse and self-integrate against without going through ECI's activation process
Known gotchas
On-premise JobBOSS2 customers and Cloud-hosted customers have different integration paths — confirm which deployment the shop is on before promising API access
Third-party integration platforms (e.g., Makini) advertise JobBOSS connectors, but these still ultimately depend on ECI-side API activation, not an independent public endpoint
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?