








































































































.webp)





















Motive (formerly KeepTruckin) is a fleet management and AI dashcam platform offering ELD compliance, GPS tracking, safety, and operations tools for trucking and logistics.
Have any questions? We’re here to help You
Testing should cover authentication, data retrieval, data writing, error handling, and workflow logic. Start by connecting a test system through Makini's authentication flow. Use sandbox or non-production instances of your target systems when available. Test API calls for each entity type you'll use (purchase orders, work orders, etc.) to verify data mapping and field coverage. Test error scenarios by providing invalid inputs or attempting operations without proper permissions. For workflow-based integrations, test each workflow step independently before testing end-to-end. Verify webhook delivery and signature verification. Test with realistic data volumes to identify performance issues. Include tests for connection failure scenarios and verify your error handling and retry logic work correctly.
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.
Makini maintains API stability and provides advance notice of breaking changes. The current API version is v1. When we introduce breaking changes, we release a new API version while maintaining the previous version for a transition period (typically 12 months minimum). Non-breaking changes (like adding new fields or endpoints) are introduced into the current version without requiring updates. We announce upcoming version changes through multiple channels: email notifications, dashboard announcements, and release notes. API responses include version information in headers. We recommend specifying the API version explicitly in your requests to ensure consistent behavior. During version transitions, we provide migration guides and support for updating integrations.
You need two essential prerequisites:
Administrator access to your NetSuite account
API Integration enabled in your NetSuite account
