← Back to all docs

E2 Shop System API

E2 Shop System—now part of JobBOSS² from ECI Software Solutions—is a job shop and custom manufacturing ERP that helps make-to-order shops manage quoting, scheduling, inventory, job costing, and shipping. An unofficial API lets you programmatically pull jobs, quotes, orders, inventory, customers, and shop-floor time, and push updates like new quotes, work orders, and material receipts back into E2.

By Alex KlarfeldMay 30, 2026
E2 Shop System API

What is E2 Shop System?

E2 Shop System is a job shop and custom manufacturing management system from ECI Software Solutions, now unified with JobBOSS into the JobBOSS² ERP platform. Make-to-order manufacturers—machine shops, fabrication, tool and die, stamping, and service shops—use E2 to optimize quoting, scheduling, inventory, and cash flow, tracking each job from estimate through production, shipping, and invoicing.

Core product areas include:

  • Order & Quoting Management (quote generation, conversion to production orders, AI-powered BOM Builder)
  • Scheduling & Production Control (drag-and-drop job scheduling, capacity planning, shop-floor tracking)
  • Inventory Management (real-time tracking, material forecasting, automated purchase orders, low-stock alerts)
  • Quality Management (equipment calibration, quality document control, CAPA workflows)
  • Job Costing & Reporting (estimated vs. actual costs, profitability by job and customer, KPI dashboards)
  • Shipping & Fulfillment (packing lists, shipping documentation, order fulfillment tracking) with QuickBooks integration

Common data entities:

  • Quotes, Estimates, Bills of Material, Routings
  • Jobs, Work Orders, Operations, Shop-Floor Time Tickets
  • Sales Orders, Purchase Orders, Packing Lists, Shipments
  • Inventory Items, Materials, Stock Locations, Receipts
  • Customers, Vendors, Contacts, Invoices, Payments
  • Work Centers, Machines, Employees, Calibration Records

The E2 Shop System Integration Challenge

Shops run mission-critical quoting, scheduling, and costing on E2 every day, but turning those workflows into reliable API-driven automation is non-trivial:

  • Cloud and on-prem editions: E2 ships in cloud-native (JobBOSS²) and legacy desktop deployments, and integration surfaces differ across them
  • Public API plus flat-file integrations: Some third-party connections run through the API while others rely on flat-file exchange, so coverage is uneven across entities
  • SDK gating: API and SDK access is provisioned per shop, requiring credentials and setup before any programmatic call is possible
  • Shop-floor data lives in mobile and kiosk apps: Time tickets and production status are captured on devices, making headless extraction non-trivial
  • Job-centric object model: Quotes, jobs, operations, and time tickets are deeply linked, so partial reads break costing and scheduling logic
  • Accounting coupling: QuickBooks and GL integrations mean financial entities must stay consistent across systems during writes

How Supergood Creates E2 Shop System APIs

Supergood reverse-engineers authenticated browser flows, the E2 / JobBOSS² public API, and shop-floor data interfaces to deliver a resilient API layer for your E2 tenant—across quoting, scheduling, inventory, and costing.

  • Handles username/password and MFA securely in a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across Quotes, Jobs, Inventory, Purchasing, and Shipping so you integrate once and rely on consistent objects
  • Aligns with your shop's custom fields, routings, and work-center configuration to keep job costing accurate

Use E2 Shop System with AI agents: E2 Shop System MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your E2 edition, modules, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready E2 adapter tailored to your shop's configuration and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as E2 and JobBOSS² evolve.

e2

API Endpoints

Authentication

POST/authenticate

Authenticate to an E2 Shop System / JobBOSS² tenant using username/password, or MFA and obtain a session token for downstream calls.

Quoting

GET/quotes

List quotes and estimates with filters for customer, status, part, and date range, including bill-of-material and routing detail.

Quoting

POST/create_quote

Create a new quote or estimate with line items, materials, and operations, ready for conversion to a production job.

Jobs

GET/jobs

Retrieve jobs and work orders with operations, scheduled work centers, time tickets, and estimated-vs-actual cost data.

Jobs

POST/create_work_order

Create a work order from a quote or sales order, assigning routings, operations, and scheduled work centers.

Inventory

GET/inventory

Pull inventory items, materials, stock locations, on-hand quantities, and receipts across the shop.

Use Cases

Sync quotes and jobs into your data warehouse

- Pull quotes, estimates, and converted jobs from E2 into a single warehouse - Stream job, operation, and shipment status to downstream BI and reporting tools - Reconcile customer and part records across systems for unified reporting

Automate quoting and order entry

- Push new quotes and estimates into E2 from your CRM or e-commerce front end - Convert accepted quotes into work orders with routings and operations - Trigger material purchase orders when a job is released to the floor

Track shop-floor production and costing

- Pull time tickets, operation status, and work-center load for real-time dashboards - Compare estimated vs. actual labor and material cost per job - Surface on-time-delivery and WIP metrics to scheduling and management tools

Keep inventory and purchasing in sync

- Sync on-hand inventory, receipts, and stock locations into planning systems - Push purchase orders and material receipts back into E2 - Alert on low-stock items and reconcile vendor invoices against POs

Technical Specifications

Authentication

Username/password and MFA handled in a managed session

Connectivity

Authenticated browser flows plus the E2 / JobBOSS² public API and SDK surfaces where exposed

Response format

Normalized JSON across Quote, Job, Inventory, Purchasing, and Shipping objects

Rate limits

Adaptive throttling tuned to your tenant to avoid shop-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for jobs, time tickets, and inventory with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for quote acceptance, job release, operation completion, and shipment events

Latency

Sub-second reads on cached entities; multi-second writes when posting through quoting and job workflows

Throughput

Horizontally scaled workers sized to high-volume job and time-ticket activity

Reliability

Retry, backoff, and idempotency keys for quote, work-order, and receipt transactions

Adaptation

Continuous monitoring of E2 and JobBOSS² releases and shop-specific configuration drift

Frequently asked questions

Yes. E2 Shop System is now unified with JobBOSS into the JobBOSS² platform, and Supergood works against the cloud-native JobBOSS² surfaces as well as legacy E2 deployments, normalizing the same job, quote, and inventory entities across both.

Supergood works with your existing E2 credentials and authenticated sessions. Where the public API or SDK is provisioned for your shop, we use it; where it isn't, we operate against the same authenticated surfaces so you don't have to wait on additional access.

Yes. Time tickets, operation status, and work-center load—including data captured through mobile and kiosk shop-floor apps—are exposed through the normalized API so you can drive dashboards and job costing programmatically.

Each shop is profiled against its configured routings, work centers, and custom fields. Supergood preserves your shop-specific structure and lifecycle states rather than forcing a generic schema, so job costing stays accurate.

Writes are coordinated with idempotency keys and validation so invoices, payments, and PO receipts stay consistent across E2 and any coupled accounting system such as QuickBooks.

Ready to get a real API?