








































































































.webp)





















NexTraq is a GPS fleet tracking software offering vehicle location, driver behavior, fuel management, and dispatching for commercial fleets.
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 uses standard HTTP status codes and structured error responses. Error responses include an error code (e.g., AUTHENTICATION_FAILED, RATE_LIMIT_EXCEEDED), error type for categorization, a human-readable error message, and a unique request ID for support inquiries. Common status codes include 400 for invalid requests, 401 for authentication failures, 403 for permission issues, 429 for rate limiting, 500 for server errors, and 503 for service unavailability. Use the error code for programmatic error handling rather than parsing error messages. The request ID helps our support team quickly identify and investigate specific issues.
Makini uses cursor-based pagination for retrieving large datasets. API responses include a next_cursor field when additional results are available. To retrieve the next page, include the cursor value in your next request: GET /api/v1/purchase-orders?cursor=CURSOR_VALUE. Cursor-based pagination is more reliable than offset-based pagination because it handles data changes between requests—if records are added or deleted while you're paginating, you won't miss records or see duplicates. Page size is configurable up to a maximum limit (typically 100-500 records per page depending on entity type). For optimal performance, use the largest page size your application can handle efficiently. The API response also includes total count when available from the source system.
If you continue to experience problems with your NetSuite M2M connection after following the troubleshooting steps, contact Makini support at support@makini.io. You can also refer to the NetSuite API Documentation and Makini Documentation for additional technical details.
