




TME Asset Management (part of TME platform) delivers enterprise asset and maintenance management tools that enable work order automation, preventive maintenance scheduling, performance monitoring, and lifecycle tracking to support reliability and planning.
Have any questions? We’re here to help You
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 webhook testing tools in the dashboard where you can trigger test webhook deliveries to verify your endpoint configuration. Test webhooks use sample payloads matching actual event structures. Verify your endpoint receives the webhook, validates the signature correctly, and responds with a 200 status code within 10 seconds. Test webhook retries by having your endpoint return error codes or timeout, then verify Makini retries as expected. Test duplicate handling by processing the same webhook multiple times. For local development, use tools like ngrok to expose your local endpoint for webhook testing. The webhook logs in the Makini dashboard show delivery attempts, response codes, and timing, helping debug delivery issues.
Yes, Makini supports write operations including creating, updating, and in some cases deleting records in connected systems. Common write operations include creating purchase orders, updating work order status, modifying inventory levels, and creating vendor records. Write support varies by system and entity type—core entities like purchase orders have comprehensive write support across major systems, while more specialized entities may have limited write support in some systems. Write operations use the same unified API, so the code to create a purchase order in SAP is identical to creating one in NetSuite. Validate write requirements during implementation to ensure your target systems support needed operations.
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.
