canonical: https://jentic.com/apis/mrpeasy.com/mrpeasy # MRPeasy API MRPeasy is a manufacturing ERP for small and mid-sized manufacturers, and its REST API exposes the production planning, inventory, and order management surface to external systems. The API covers bills of materials, customer orders, manufacturing orders, purchase orders, RMA orders, customers, products, and parameter data so production schedules, stock movements, and order fulfilment can be driven from outside the MRPeasy UI. With 70 endpoints across the major resources it supports both reads and writes for end-to-end manufacturing workflows. ## For AI agents Run manufacturing operations end-to-end - create customer orders, schedule manufacturing orders, manage bills of materials, and track stock - through the MRPeasy ERP API. ## Scope Does not handle accounting ledgers, payroll, or shipping label generation - use for manufacturing ERP order, BOM, and inventory operations only. ## Capabilities - Create and update bills of materials with components, routings, and cost data via /boms - Place and amend customer orders with line items and shipping detail via /customer-orders - Schedule manufacturing orders against existing BOMs via /manufacturing-orders - Maintain customer master data and contact records via /customers - Issue and reconcile purchase orders to suppliers via /purchase-orders - Process returns and warranty cases through /rma-orders - Configure product groups, parameters, and routings that drive production planning ## Use cases ### Connect E-Commerce Orders to Production Storefronts on Shopify or BigCommerce drop sales orders into MRPeasy as customer-orders, and MRPeasy schedules a matching manufacturing-order against the BOM. The integration removes manual order entry for built-to-order manufacturers and tightens lead time accuracy. A typical bridge writes to POST /customer-orders on every paid checkout and POST /manufacturing-orders for any product flagged as make-to-order. Example prompt: On checkout, call POST /customer-orders with the order lines and POST /manufacturing-orders for any made-to-order SKU referencing the matching BOM. ### Automate Purchase Order Replenishment Procurement teams trigger purchase orders when component stock falls below reorder thresholds. The MRPeasy API exposes /boms to read component requirements and /purchase-orders to issue the replenishment to the right supplier. A scheduled job converts low-stock alerts into approved purchase orders with no manual data entry, reducing stockouts on the shop floor. Example prompt: For every component below reorder point, call POST /purchase-orders with the supplier id and quantity equal to economic order quantity from the BOM record. ### Bill of Materials Sync from PLM Engineering teams maintain product structures in a PLM tool and push approved revisions into MRPeasy through the /boms endpoints. The integration ensures that the shop floor builds against the latest released BOM and that costing reflects the current component list. Two-way sync via GET `/boms/{id}` and PUT `/boms/{id}` keeps the production system aligned with engineering. Example prompt: On PLM release, call PUT `/boms/{id}` with the new component list and routing, and audit by re-reading GET `/boms/{id}.` ### Agent-Driven Order Status Lookup for Sales A sales agent answers a customer's 'where is my order?' question by querying MRPeasy through Jentic. The agent searches for 'check manufacturing order status', loads the schema, and calls GET `/manufacturing-orders/{id}` for the linked production order. Response includes the scheduled completion date and current status, which the agent relays to the customer in the chat. Example prompt: Search Jentic for 'check manufacturing order status', load the manufacturing-orders schema, and call GET `/manufacturing-orders/{id}` for the order id surfaced from the customer message. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/boms` | List bills of materials | | POST | `/customer-orders` | Create a customer order | | POST | `/manufacturing-orders` | Schedule a manufacturing order against a BOM | | POST | `/purchase-orders` | Issue a supplier purchase order | | GET | `/customers` | List customer master records | | POST | `/rma-orders` | Open a return or warranty case | ## Key resources - **Bills of Materials** — Component lists, routings, and costing for each manufactured product - **Customer Orders** — Sales orders with line items, shipping, and payment metadata - **Manufacturing Orders** — Scheduled production runs against a specific BOM - **Purchase Orders** — Supplier replenishment orders - **Customers** — Customer master data and contact records - **RMA Orders** — Return and warranty processing for finished goods ## Why Jentic - **Setup:** Wiring MRPeasy by hand means building its basic-auth header, targeting the rest/v1 host, and mapping BOM, order, and inventory actions across its endpoints. Through Jentic you install once, import the MRPeasy API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** MRPeasy carries its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as reading BOMs or customers. You choose the operations it may call, so writes like creating manufacturing or purchase orders are not included unless you add them. - **Credential handling:** Your MRPeasy Basic auth credentials are stored once, encrypted, by your own Jentic One instance and used to build the Authorization header at execution time. The raw username and password never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a manufacturing order' or 'list customer orders', and Jentic returns the matching MRPeasy operation with its input schema, so the agent calls the right endpoint without reading MRPeasy's REST docs. ## Related APIs - **Katana MRP API** — Katana MRP is a competing manufacturing ERP for small batch makers - **Zoho Inventory API** — Zoho Inventory handles stock and order management without full MRP scheduling - **HubSpot CRM Contacts** — HubSpot stores the customer record that an MRPeasy customer-order references ## FAQ ### What authentication does the MRPeasy API use? The MRPeasy API uses HTTP Basic authentication scoped to your account. Through Jentic the username and password are held in the encrypted vault and injected at execution, so the credentials never appear in the agent's prompt context. ### Can I create a manufacturing order against an existing BOM? Yes. POST /manufacturing-orders takes the product id and quantity and uses the linked BOM at `/boms/{id}` to plan components and routing. Combine with POST /customer-orders to bridge a sales order into production in one workflow. ### What are the rate limits for the MRPeasy API? MRPeasy applies per-account throttling and recommends paginating list endpoints rather than fetching every record on each call. Use the offset and limit parameters on list endpoints like GET /boms and GET /customer-orders to stay inside the throttle window. ### How do I bridge an e-commerce order to production through Jentic? Search Jentic for 'create a manufacturing order in mrpeasy', load the customer-orders schema, call POST /customer-orders with the cart, then POST /manufacturing-orders for any made-to-order line. Two operations, no direct credential handling in the agent. ### Is the MRPeasy API free? No. API access is included with paid MRPeasy subscriptions. Plan-level limits gate the number of users and the volume of records you can hold in the system, but there is no separate per-call charge for API use. ### Can the API process returns and RMAs? Yes. POST /rma-orders opens a return case against the original customer order and tracks it through inspection and resolution. Status changes are exposed via GET `/rma-orders/{id}` for downstream support tooling. ### Can I limit what my agent is allowed to do with the MRPeasy API? Yes. Jentic One is self-hosted, so you run your own instance and your own rules decide which MRPeasy operations and credentials the agent may use. You can allow read-only calls such as GET /boms and GET /customers while withholding writes like POST /manufacturing-orders and POST /purchase-orders, since MRPeasy carries its targets in the request body rather than the URL path and only the operations you enable are callable. Your Basic auth credentials are stored by your own instance and used to build the request at execution time, never entering the agent's prompt.