








































































































.webp)





















42Q is a cloud-native manufacturing execution system providing production tracking, quality, traceability, and analytics for global electronics, medical device, and discrete manufacturers.
Have any questions? We’re here to help You
API tokens must be stored securely and should never be exposed on the client side or in public repositories. Store tokens in secure environment variables or dedicated secrets management systems like AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault. Never hardcode tokens in application code or commit them to version control. Implement proper access controls so only authorized services can access stored tokens. For production environments, use separate tokens from development/testing environments. Rotate tokens periodically and immediately revoke tokens if you suspect they've been compromised. Makini tokens provide access to customer data, so treat them with the same security standards you'd apply to database credentials.
500-level errors indicate issues on Makini's side or with the connected system. These are typically temporary and retrying the request after a brief delay often succeeds. Implement exponential backoff for retries—wait a few seconds, then progressively longer intervals. If errors persist beyond a few retries, check the Makini status page for service disruptions. The error may also stem from the connected system experiencing issues rather than Makini itself. For persistent 500 errors, contact support with the request ID from the error response. Include details about when the error started, which operations are affected, and which connections are impacted. Our support team can quickly identify whether the issue is systemic or connection-specific.
Makini monitors connection health continuously and provides multiple ways to detect reauthorization needs. The connection status endpoint returns the current state including whether reauthorization is required. Makini sends webhooks when connections enter a state requiring reauthorization, allowing proactive notification. API requests to a connection requiring reauthorization return specific error codes prompting reconnection. The Makini dashboard displays connection status across all customers. Best practice is to implement webhook listeners for connection status changes and proactively notify customers when reauthorization is needed, rather than waiting for operations to fail. Include clear instructions on how to reconnect in your notification.
When a system becomes unavailable, Makini detects the connectivity failure and marks the connection status accordingly. Scheduled syncs will fail with connectivity errors. API requests to the connection will return error responses indicating the system is unreachable. Makini continues attempting scheduled syncs using exponential backoff—initial retries happen frequently, then progressively less often to avoid overwhelming the system when it comes back online. Webhooks notify you of the connection status change. When the system comes back online, normal operations resume automatically. For temporary outages, no action is required. For extended outages, you may want to notify the customer. Connection credits remain consumed during outages since the connection configuration persists.
