




Maxpanda CMMS is a cloud-based computerized maintenance management system (CMMS) that helps organisations manage work orders, schedule preventive maintenance, track assets and inventory, and centralise maintenance operations with configurable views and mobile access. It supports real-time maintenance tracking and is used across facilities, healthcare, education, and other sectors.
Have any questions? We’re here to help You
Makini supports over 2,000 industrial systems across ERP, CMMS, and WMS categories. This includes major platforms like SAP (ECC, S4/HANA, Business One), Oracle NetSuite, Microsoft Dynamics, IBM Maximo, and specialized industrial systems. We support both cloud-based and on-premises installations. If you need to connect to a system we don't currently support, we're committed to building that integration for you at no additional charge—most new integrations are completed within one business day. You can view our full list of supported systems at makini.io/integrations.
All Makini webhooks include a signature header for verification. The signature is an HMAC hash of the webhook payload using your webhook secret as the key. To verify a webhook, compute the HMAC using your secret and compare it to the signature header using constant-time comparison to avoid timing attacks. Never process webhook data without verification, as this could expose your system to forged requests. Your webhook secret is provided when you configure webhooks and should be stored securely. Webhook verification ensures that only legitimate requests from Makini are processed by your application.
Testing should cover authentication, data retrieval, data writing, error handling, and workflow logic. Start by connecting a test system through Makini's authentication flow. Use sandbox or non-production instances of your target systems when available. Test API calls for each entity type you'll use (purchase orders, work orders, etc.) to verify data mapping and field coverage. Test error scenarios by providing invalid inputs or attempting operations without proper permissions. For workflow-based integrations, test each workflow step independently before testing end-to-end. Verify webhook delivery and signature verification. Test with realistic data volumes to identify performance issues. Include tests for connection failure scenarios and verify your error handling and retry logic work correctly.
Makini provides several debugging tools. The dashboard shows detailed request logs including request/response payloads, headers, status codes, and timing. Each API request generates a unique request ID included in responses—provide this when contacting support for faster investigation. For workflow-based integrations, Makini Flows includes execution logs showing each step's input/output, timing, and any errors. Connection health monitoring shows sync history, error rates, and connection status over time. API responses include detailed error information with error codes and messages. For development, we recommend using API clients like Postman or Insomnia to interactively test API calls and inspect responses. Our API documentation includes request/response examples for all endpoints.
