




















































































VAI S2K Warehouse Management extends the S2K ERP suite for distributors with paperless picking, putaway, cycle counting, and shipping on mobile and RF devices.
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.
Yes, you can trigger syncs manually through both the API and the Makini dashboard. The API provides endpoints to initiate syncs for specific entities (purchase orders, work orders, etc.) on a given connection. Manual syncs are useful when you need immediate data updates outside the regular schedule, when onboarding new customers, or when recovering from sync failures. Manual syncs follow the same incremental logic as scheduled syncs, retrieving only changed records since the last successful sync. You can also trigger full re-syncs that ignore the last sync timestamp and retrieve all records within the configured historical period.
Makini provides several performance monitoring capabilities. API responses include timing information showing request processing time. The dashboard includes performance metrics showing average response times, throughput, and error rates over time. You can set up alerts for performance degradation or error rate increases. Each request generates a unique request ID that enables detailed performance analysis. For workflow-based integrations, execution logs show per-step timing, helping identify bottlenecks. We recommend implementing client-side monitoring to track end-to-end latency including network time. Monitor trends over time rather than individual requests—occasional slow requests are normal, but sustained increases may indicate issues requiring investigation.
"Web services only role" is an optional security setting that restricts the role to only accessing NetSuite via web services (APIs), preventing UI login. This is recommended for integration roles as it enhances security by limiting the access method to API-only usage.
