








































































































.webp)





















Ciranet provides quality, EHS, and compliance management software for regulated industries, supporting document control, training, audits, and change management.
Have any questions? We’re here to help You
Makini provides a /sync-status API endpoint that returns the current synchronization state for a connection. The response includes the last successful sync timestamp, sync status (in progress, completed, failed), any error messages, and the next scheduled sync time. You can query this endpoint to monitor sync health and detect issues. For workflow-based syncs using Makini Flows, each workflow execution is logged with detailed status information including start time, completion time, success/failure status, and any errors encountered. The Makini dashboard also provides visual sync status monitoring across all connections.
Design your webhook receiver to handle duplicates and out-of-order webhooks, as network issues or retries can cause both scenarios. Keep the receiver lightweight—ideally writing incoming webhooks to a queue or reliable storage—then process them asynchronously. This prevents timeouts and allows your system to handle high-volume webhook spikes. Respond with a 200 status code immediately after receiving the webhook, before processing begins. Implement idempotency by tracking processed webhook IDs and skipping duplicates. Use constant-time comparison for signature verification to prevent timing attacks. If webhook processing fails, log the error but still return 200 to prevent unnecessary retries. Set up monitoring and alerts for webhook failures so you can investigate issues promptly. For critical workflows, combine webhooks with periodic polling as a fallback mechanism.
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.
You need two essential prerequisites:
Administrator access to your NetSuite account
API Integration enabled in your NetSuite account
