Reference · built on requestConnectorPLC, SCADA & MES

Fulcrum

Sales orders, jobs, operations, inventory, shipments, and NCRs from the Fulcrum Public API for job shops.

Request accessPricing ↗

About

Fulcrum is a cloud ERP and MES for job shops. Its Public API is a REST interface at api.fulcrumpro.com, or api.fulcrumpro.us for ITAR sites, described by an OpenAPI schema. Resources cover quotes, sales orders, jobs, items to make and their operations, inventory, receiving, shipments, work orders, equipment, timers, NCRs, CAPAs, tool calibrations, and report-ready views.

Through Fibric, an operator reads jobs and their tracking, shipments, and inventory on a schedule and proposes changes: move a job to hold, adjust a priority or due date, open an NCR, or draft a purchase order. You approve each one. The connector sends it once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Fulcrum and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sales orders and their line items through POST /api/sales-orders/list, GET /api/sales-orders/{salesOrderId}, and the Sales Order Part Line Item routes
  • Jobs with status, tracking, operations, and in-process checkpoints through /api/jobs/list, /api/jobs/{jobId}/tracking, and /api/jobs/{jobId}/operations/list
  • On-hand and available quantities through GET /api/inventory/byItem and /api/inventory/availableByItem, plus inventory events and lots
  • Shipments with scheduled ship-by and actual shipped dates through /api/shipments/list and /api/shipment-line-items/list
  • NCRs, CAPAs, and tool calibration records through their list and get routes
  • Report-ready rows under /api/reporting: job-activity, sales-order-lines, shipping, material-requirements, inventory, and time-clock
  • Equipment and work centers through /api/equipment/list and /api/work-centers/list

Proposed actions

  • Target capability: propose a job status change such as hold, approved, scheduled, or cancelled through POST /api/jobs/{jobId}/status
  • Target capability: propose a priority or due date change through PATCH /api/jobs/{jobId}
  • Target capability: propose opening an NCR through POST /api/ncrs, or a CAPA through POST /api/capas
  • Target capability: propose a draft purchase order through POST /api/purchase-orders
  • Target capability: propose a message on a job's chat through POST /api/jobs/{jobId}/messages

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a job behind a failed inspection

    An NCR opens against a job. The operator proposes status hold on that job and a message on its chat naming the NCR. You approve; the receipt records both calls.

    With Quality Hold

  • Warn before a ship-by date slips

    Open shipments are compared with their jobs' quantityCompleted and quantityToMake. Where a job cannot finish by the scheduled ship-by date, the operator drafts a customer notice for approval.

    With Promise Date, Order Risk

  • Reorder from can-make math

    availableByItem and /api/items/{itemId}/can-make show what the shop can build from stock. When a required item falls short, the operator proposes a draft purchase order for review.

    With Reorder Point, Purchase Order Draft

  • Rank the backlog by risk

    Jobs in inProgress and scheduled are read with their tracking. The operator proposes priority changes through PATCH /api/jobs/{jobId}, one per job, each approved on its own.

    With Backlog Priority

Requirements

  • A Fulcrum site and a Public API token with a name, description, and expiration date; a token is revoked by deleting it
  • For user-bound tokens, the Fulcrum permission each route checks, such as Create NCR or Edit CAPA
  • ITAR sites use api.fulcrumpro.us; their tokens receive 401 on the .com host
  • Optionally, a client generated from the OpenAPI schema at api.fulcrumpro.com/swagger/v1/swagger.json
Authentication
A bearer token generated in your Fulcrum site under Business Setup, System Data, Public Api, sent in the Authorization header on every request.

Limits

  • The Developer Hub publishes no webhook or rate-limit documentation; Fibric polls list routes and filters on modifiedAfterUtc where a route offers it
  • add-quantity-completed adds the quantity again on every call; a retry after a timeout must first read the operation
  • NCR and tool calibration creates are not repeat-safe: a retried request opens a second record
  • Retroactive timer blocks may not be in the future, older than 30 days, or longer than 7 days

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fulcrum ↗

Questions and answers

How does a request authenticate?
With a bearer token in the Authorization header. Tokens are created in your Fulcrum site under Business Setup, System Data, Public Api, each with a name, description, and expiration date. Deleting a token revokes it. GET /api/auth/validate returns details about the token in use.
Which job statuses can the API set?
JobStatusEnum lists draft, needsReview, approved, engineering, scheduled, inProgress, complete, cancelled, and hold. POST /api/jobs/{jobId}/status takes one of them. createPOs is required for Engineering and Approved; isInitialDataImport is required for Complete.
Does Fulcrum also have an MCP server?
Yes. Fulcrum documents an MCP server at https://YOUR-SITE.fulcrumpro.com/api/mcp, reached with OAuth or an MCP API key, behind a feature flag your Fulcrum contact enables. This listing uses the Public API, not the MCP server.
Ask about Fulcrum

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Fulcrum through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy