




























































































.webp)










Maintenance Connection is a CMMS/EAM solution used to track assets, work orders and inventory across multiple sites, enabling organizations to standardize preventive maintenance and reduce unplanned downtime.
Have any questions? We’re here to help You
Our standard SLA targets 99.9% uptime for cloud deployments, which translates to less than 9 hours of downtime per year. For enterprise customers with critical integration requirements, we offer enhanced SLAs up to 99.99% through multi-region redundancy and dedicated infrastructure. SLAs cover the Makini platform itself—availability of connected third-party systems is outside our control, though we monitor their health and alert you to issues. For self-hosted deployments, uptime depends on your infrastructure configuration, and we provide architecture guidance to help you achieve your availability targets. We maintain a public status page showing real-time system health and incident history.
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.
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.
Authentication errors (401 status code) typically occur for a few reasons: the API token is invalid or expired, the underlying system credentials have changed, the system requires reauthorization, or the token lacks necessary permissions. First, verify you're including the token correctly in the Authorization header. Check the connection status in the Makini dashboard—if it shows as requiring reauthorization, the customer needs to reconnect. If credentials were recently changed in the source system, you'll need to reconnect to obtain a new token. For persistent issues, check if the system account has sufficient permissions to perform the requested operation. If the problem continues, contact support with the request ID for investigation.
