








































































































.webp)





















I.D. Systems, now part of PowerFleet, provides industrial fleet and asset management solutions including forklift, vehicle, and yard telematics.
Have any questions? We’re here to help You
Makini is SOC 2 Type 2 compliant and undergoes penetration testing twice annually. We use industry-standard encryption protocols including TLS 1.2+ for data in transit and AES-256 for data at rest. Customer credentials are encrypted using secure key management practices. Our infrastructure follows security best practices including network segmentation, access controls, and regular security audits. For highly regulated industries or customers with strict compliance requirements, we offer self-hosted deployment options that keep all data within your infrastructure. We've successfully met security requirements for enterprises including financial institutions and government contractors.
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.
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.
Yes, through Makini Flows, which includes connectors for popular databases including Snowflake, PostgreSQL, MySQL, MongoDB, and others. This enables workflows that synchronize data between industrial systems and your data warehouse or analytics platforms. For example, you can sync purchase orders from SAP to Snowflake for analytics, or use database queries to drive integration logic. Database integrations use the same workflow builder as other integrations, making it easy to combine industrial system data with database operations. For direct database-to-database syncing, we can help design optimized workflows. Database connections are treated as custom integrations and may require additional workflow development.
