




Express Maintenance is a CMMS solution designed for the shop floor that helps track and manage work orders, increase technician wrench-time and maintain audit-ready records in manufacturing operations.
Have any questions? We’re here to help You
When customers change their system credentials, the existing Makini connection will lose access and workflows will begin failing with authentication errors. Makini provides webhook notifications when connections require reauthorization, allowing you to proactively notify customers. Customers can reconnect by logging into the system through Makini's authentication flow again, which issues a new API token. The reconnection process takes only a few minutes. Best practice is to implement connection health monitoring and automated alerts when connections require attention, so you can address issues before they impact operations.
Makini's API supports date filtering on most endpoints using query parameters. You can filter by creation date, modification date, or entity-specific date fields like order date or delivery date. Common patterns include `modified_after=2024-01-01` to retrieve records updated since a specific date, or relative timestamps like `modified_after=2024-01-01T00:00:00Z`. For optimal performance, use incremental data retrieval patterns rather than repeatedly fetching all records. The sync status endpoint provides the last sync timestamp, which you can use as the `modified_after` value for your next query. This approach minimizes data transfer and API load while ensuring you capture all changes.
Makini sends webhooks for several event types: sync completion (successful or failed), connection authentication required (when credentials need renewal), connection status changes (online/offline), and system errors requiring attention. Each webhook payload includes the event type, timestamp, connection ID, and event-specific details like error messages or affected entities. You can configure which events trigger webhooks on a per-connection basis. For workflow-based integrations using Makini Flows, you can also set up custom webhooks triggered by specific conditions in your business logic, providing granular control over real-time notifications.
Disconnecting a connection can be done through the Makini dashboard or API. In the dashboard, navigate to the connection and select disconnect. Via API, call the disconnect endpoint with the connection ID. Disconnecting immediately invalidates the API token and stops all scheduled syncs and workflows for that connection. The connection credits used are returned to your pool and become available for new connections. Disconnecting does not delete historical data that was previously synced—that remains accessible until you choose to delete it. Customers can reconnect the same system at any time, which will create a new connection with a new API token. Use disconnection for customers who churn or when permanently retiring a connection.
