Limitations & Data Integrity

This section outlines how Leanmote API ensures system stability and data reliability during integration.

Rate Limiting

To protect service availability and ensure fair usage, we recommend the following limits:

• ⏱️ Max 100 requests per minute per organization.
• 🚫 Excessive requests may be throttled or temporarily blocked.

Tips:

• Use batch endpoints where available (e.g., POST /tasks with arrays).
• Implement retries with exponential backoff in case of 429 responses.

Data Integrity Principles

Leanmote enforces strict rules to preserve consistency across your data:

• 🔄 Atomic Transactions: Each operation is fully completed or rolled back to prevent partial data.
• 🔗 Hierarchical Relationships: Tasks, statuses, and logs must belong to a valid project within a valid organization.
• 🛡️ Referential Integrity: IDs (e.g., project_app_id, task_app_id) must resolve to existing objects in the system.
• ✅ Scope Validation: Every request is validated against the token’s associated organization.
• 🧠 Duplicate Detection: Logs and tasks already processed will be ignored to prevent duplication.

Following these practices helps avoid errors and ensures consistent, accurate data in your Leanmote workspace.