








































































































.webp)





















Logility, now part of Aptean, provides supply chain planning software for demand, inventory, supply, and S&OP across manufacturing, distribution, and retail.
Have any questions? We’re here to help You
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.
The RATE_LIMIT_EXCEEDED error indicates you've exceeded the API rate limit for the connection or account. Rate limits are typically set per connection and per time window (usually per minute). When you hit a rate limit, the response includes a Retry-After header indicating when you can retry the request. Implement exponential backoff in your retry logic to avoid immediately hitting the limit again. If you consistently hit rate limits, review your API usage patterns—you may be making unnecessary requests, polling too frequently, or could benefit from webhook-based synchronization. For legitimate high-volume needs, contact us to discuss increasing your rate limits.
Makini provides several debugging tools. The dashboard shows detailed request logs including request/response payloads, headers, status codes, and timing. Each API request generates a unique request ID included in responses—provide this when contacting support for faster investigation. For workflow-based integrations, Makini Flows includes execution logs showing each step's input/output, timing, and any errors. Connection health monitoring shows sync history, error rates, and connection status over time. API responses include detailed error information with error codes and messages. For development, we recommend using API clients like Postman or Insomnia to interactively test API calls and inspect responses. Our API documentation includes request/response examples for all endpoints.
Makini monitors connection health continuously and provides multiple ways to detect reauthorization needs. The connection status endpoint returns the current state including whether reauthorization is required. Makini sends webhooks when connections enter a state requiring reauthorization, allowing proactive notification. API requests to a connection requiring reauthorization return specific error codes prompting reconnection. The Makini dashboard displays connection status across all customers. Best practice is to implement webhook listeners for connection status changes and proactively notify customers when reauthorization is needed, rather than waiting for operations to fail. Include clear instructions on how to reconnect in your notification.
