MRPeasy API Documentation
This is the complete API documentation for connecting to the MRPeasy API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet MRPeasy: MRPeasy manufacturing ERP app draft scaffolded for one-shot validation. Basic auth uses API key as username and API secret as password. Keep reading to get started.
Quickstart
Before you run your first MRPeasy request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one MRPeasy connection — create or choose one in Connections. Note its
connectionId.
Every MRPeasy action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/mrpeasy/latest/actions/{actionSlug}You need a MindCloud API Key and a MRPeasy connection. Then call an action such as Get BOM:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/mrpeasy/latest/actions/get-bom" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected MRPeasy account that should run the action. MindCloud stores and refreshes the MRPeasy credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
MRPeasy actions
All 38 published actions for this MRPeasy version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate BOM
- POSTCreate Customer
- POSTCreate Customer Order
- POSTCreate Item
- POSTCreate Manufacturing Order
- POSTCreate Routing
- DELETEDelete BOM
- DELETEDelete Item
- DELETEDelete Manufacturing Order
- DELETEDelete Routing
- GETGet BOM
- GETGet Customer
- GETGet Customer Order
- GETGet Item
- GETGet Manufacturing Order
- GETGet Product Group
- GETGet Purchase Order
- GETGet Routing
- GETGet Shipment
- GETGet Unit
- GETGet Vendor
- GETList BOMs
- GETList Customer Orders
- GETList Customers
- GETList Items
- GETList Manufacturing Orders
- GETList Product Groups
- GETList Purchase Orders
- GETList Routings
- GETList Shipments
- GETList Units
- GETList Vendors
- PUTUpdate BOM
- PUTUpdate Customer
- PUTUpdate Customer Order
- PUTUpdate Item
- PUTUpdate Manufacturing Order
- PUTUpdate Routing
Related apps
More Commerce apps on the Universal API, behind the same REST shape. Or browse all apps.