← Back to all docs

ProShop API

ProShop is a 100% paperless, web-based ERP/MES/QMS platform built for manufacturing machine shops, combining quoting, work orders, scheduling, purchasing, inventory, and quality into one integrated system. An unofficial API lets you programmatically pull parts, work orders, job costs, purchase orders, inventory, and inspection records—and push updates like new quotes, jobs, and POs back into ProShop.

By Alex KlarfeldMay 30, 2026
ProShop API

What is ProShop?

ProShop is a 100% paperless, fully web-based ERP, MES, and QMS platform purpose-built for small-to-medium manufacturing machine shops. Shops use ProShop to manage the full job lifecycle—quoting and estimating, parts and routings, work orders, real-time scheduling, purchasing, inventory, equipment and tooling, and integrated quality management—across more than 30 connected modules, accessed entirely through a browser with no desktop installs. It is also widely used to support ISO, AS9100, and CMMC compliance for shops serving aerospace, defense, and other regulated industries.

Core product areas include:

  • Parts module — single source of truth for part specs, routings, drawings, and work instructions
  • Work Orders — current and past job details with full cross-department visibility
  • Estimating & quoting, BOMs, and work plans integrated directly into job workflows
  • Real-time scheduling, job costing, purchasing, and inventory
  • Integrated QMS capturing inspection data as work happens for traceability and audits
  • Equipment, tooling, fixtures, COTS, RTAS, messaging, and dashboards

Common data entities:

  • Parts, Routings, Drawings, Work Instructions
  • Work Orders, Jobs, Operations, Time Tracking
  • Quotes, Estimates, BOMs
  • Purchase Orders, Vendors, Receiving
  • Inventory, Lots, Materials, COTS
  • Inspections, Quality Records, Non-Conformances, Job Costs
  • Equipment, Tooling, Fixtures, Customers

The ProShop Integration Challenge

Machine shops run mission-critical operations on ProShop daily, but turning its browser-driven, deeply integrated workflows into API-driven automation is non-trivial:

  • No public developer API: ProShop is web-based with no documented, general-purpose REST API for third-party developers to build against
  • Deployment variability: Shops run cloud-hosted or on-premise instances, each with different network access and URL patterns
  • Tightly coupled modules: Parts, work orders, quality, and job costing share state, so reads and writes must respect cross-module dependencies and routings
  • Point integrations only: Out-of-the-box connections target specific tools like QuickBooks, Sage, Paperless Parts, and Datanomix—not arbitrary systems
  • Session-based access: Data lives behind authenticated browser sessions rather than token-based API endpoints
  • Compliance sensitivity: Shops running CMMC, ISO, and AS9100 workflows require careful, audit-friendly access to quality and traceability records

How Supergood Creates ProShop APIs

Supergood reverse-engineers ProShop's authenticated browser flows to deliver a resilient, token-accessible API layer for your ProShop instance—whether it's cloud-hosted or on-premise.

  • Handles username/password and MFA login securely in a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across Parts, Work Orders, Purchasing, Inventory, and Quality so you integrate once against consistent objects
  • Respects cross-module dependencies and your shop's routings, custom fields, and compliance records

Use ProShop with AI agents: ProShop MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, deployment model, and authentication setup.

  • Supergood Generates and Validates Your API

We deliver a production-ready ProShop adapter tailored to your instance and workflows.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as ProShop evolves.

proshop

API Endpoints

Authentication

POST/authenticate

Authenticate to a ProShop instance using username/password (and MFA where enabled) and obtain a session token for downstream calls.

Parts

GET/parts

List parts with their specs, routings, drawings, and work instructions, filtered by customer, status, or revision.

Work Orders

GET/work_orders

Retrieve work orders and jobs with operations, schedule status, and cross-department progress.

Work Orders

POST/create_work_order

Create a new work order or job against an existing part and routing.

Purchasing

GET/purchase_orders

Pull purchase orders, vendors, and receiving records across open and closed POs.

Inventory

GET/inventory

Query on-hand inventory, lots, and materials with quantity and location detail.

Use Cases

Sync job and part data into a central warehouse

- Pull parts, routings, and work instructions into a single source of truth for analytics - Stream work order status and operation progress to BI and dashboards - Reconcile job-cost actuals against quotes and estimates

Automate purchasing and inventory workflows

- Pull purchase orders, vendors, and receiving records into procurement tools - Trigger material reorders when inventory and lot quantities cross thresholds - Sync vendor and material data with external ERP and accounting systems

Surface quality and compliance records

- Extract inspection data, non-conformances, and traceability records for audits - Feed CMMC, ISO, and AS9100 evidence into compliance reporting tools - Alert on failed inspections and open quality actions in real time

Streamline quoting and estimating

- Push new quotes and estimates into ProShop from CRM or sales tools - Pull BOMs and work plans for downstream pricing and capacity planning - Route accepted quotes into work orders without manual re-entry

Technical Specifications

Authentication

Username/password and MFA handled in a managed session

Connectivity

Authenticated browser flows against your cloud-hosted or on-premise ProShop instance

Response format

Normalized JSON across Parts, Work Orders, Purchasing, Inventory, and Quality objects

Rate limits

Adaptive throttling tuned to your instance to avoid server-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for parts, work orders, 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 work order status, inventory changes, inspection results, and PO updates

Latency

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

Throughput

Horizontally scaled workers sized to your shop's job and transaction volume

Reliability

Retry, backoff, and idempotency keys for work order, PO, and inventory transactions

Adaptation

Continuous monitoring of ProShop releases and instance-specific configuration drift

Frequently asked questions

ProShop does not publish a general-purpose developer API. It offers specific point integrations (such as QuickBooks, Sage, Paperless Parts, and Datanomix), so Supergood builds a resilient API layer over your authenticated ProShop sessions to give you programmatic access to the data you need.

Yes. Supergood adapts to either deployment model. For cloud-hosted instances we work against your tenant; for on-premise setups we operate against the same authenticated surfaces with network configuration tuned to your environment.

Yes. Inspection data, non-conformances, and traceability records from ProShop's integrated QMS are exposed through the normalized API, with audit logging to support CMMC, ISO, and AS9100 workflows.

Yes. Beyond reads, the API supports writes such as creating quotes, work orders, and purchase orders, while respecting ProShop's cross-module dependencies and your shop's routings.

Supergood normalizes data across modules like Parts, Work Orders, Purchasing, Inventory, and Quality so you integrate once against consistent objects rather than reconciling each module separately.

Ready to get a real API?