# MRPeasy API documentation: authentication, endpoints and examples > Source: https://netray.co/erp-help/mrpeasy-api-documentation-rest-authentication-endpoints > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer The MRPeasy REST API returns JSON over HTTPS and is authenticated with an API key and secret that you generate in your account. You read and write resources such as customer orders, manufacturing orders, items and stock, and page through lists with a Range header. Always confirm the exact resource names against MRPeasy's own API documentation. ## Kind how-to ## System small-erp ## Erp MRPeasy ## Module REST API ## Query mrpeasy api documentation ## Alternate Queries - mrpeasy rest api - mrpeasy api authentication - mrpeasy api customer orders items - mrpeasy api example ## Applies To MRPeasy cloud accounts where API access is enabled for the user. The REST API is versioned, so use the version path shown in the current documentation. ## Steps ### How to call the MRPeasy API **Items:** - Sign in as an administrator and open the API settings in your user or system settings to generate an API key and secret. - Keep the secret in a secrets manager. Treat it like a password and create separate keys for separate integrations. - Open the official API documentation and pick the resource, for example customer orders, items or stock. - Send a GET request over HTTPS using HTTP Basic authentication with the key as user name and the secret as password. - For lists, add a Range header such as items=0-99 and read the Content-Range response header to continue paging. - To create or change data, send a POST or PUT with a JSON body that follows the documented fields, then read the response for validation errors. - Respect the rate limit stated in the documentation. Back off and retry when you receive a 429 response. - Log the status code and body of every non-2xx response so failures can be diagnosed. ## Sections ### Authentication details **Body:** MRPeasy uses a key and secret pair rather than a user password in the integration. Because the key inherits access from the account that created it, create the key from a user whose permissions match the job. A reporting integration should not hold write access to orders. Rotate keys when staff change, and revoke any key that appears in a shared repository or ticket. **Code:** - curl -s -u ':' \ -H 'Accept: application/json' \ -H 'Range: items=0-49' \ 'https://app.mrpeasy.com/rest/v1/customer-orders' ### Common resources and uses **Body:** Typical resources include customer orders, manufacturing orders, items, products with bills of materials, purchase orders, stock and customers. Teams use them to import web-store orders, export production status to a dashboard, or sync stock levels to an e-commerce channel. Not every field is writable. Status transitions and costs are often controlled by MRPeasy's own logic, so create a record and let the system move it through its workflow rather than forcing values. ### Paging, filtering and errors **Body:** A list call returns a partial response with the range you asked for. Loop until the Content-Range total is reached. Add filters from the documentation, such as a modified-since filter, to keep runs short. Handle 400 responses as data problems (read the message and fix the payload), 401 or 403 as credential or permission problems, and 429 or 5xx as retry cases. ### Design tips **Body:** - Sync incrementally and reconcile fully once a night. Store the MRPeasy id next to your system's id so updates are idempotent. - Where you only need a few automations, a connector platform such as Zapier or Make can call the same API without custom code. ## Pitfalls - Putting the API secret in browser code or a public repository. - Ignoring the Range header and assuming one call returns every record. - Polling too frequently and hitting rate limits. - Writing status or cost fields that MRPeasy expects to calculate itself. - Using one shared key for every integration, which makes revocation disruptive. ## Ai Angle A read-only assistant on top of the MRPeasy API can answer questions like 'which customer orders ship this week and are short of material' by calling the right list endpoints, joining the results and showing the calls it made. A model hosted on your own server means order and cost data is not sent to a third-party AI service, and any write-back, such as creating a purchase order, waits for a person to approve. ## Faq ### Does MRPeasy have a REST API? **Answer:** Yes. MRPeasy provides a REST API with JSON responses for resources such as customer orders, items and stock. Access requires an API key and secret created in your account. ### How do I authenticate to the MRPeasy API? **Answer:** Use HTTP Basic authentication over HTTPS, with the API key and secret generated in your MRPeasy settings. Create the key from a user with only the permissions the integration needs. ### How does MRPeasy paging work? **Answer:** Send a Range header such as items=0-99 to request a slice. The response includes a Content-Range header with the total, which tells you whether more pages remain. ### Is there an API rate limit? **Answer:** Yes, limits apply. Check the number in the current documentation, throttle your client, and retry with backoff when you get a 429 response. ## Search terms mrpeasy api documentation, mrpeasy rest api, mrpeasy api key, mrpeasy customer orders api, mrpeasy items api, mrpeasy stock api, mrpeasy api example, mrpeasy developer --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json