Blame
|
1 | # Rate Limits |
||||||
| 2 | ||||||||
|
3 | Rate Limits protect AeThex services from overload, abuse, accidental loops, and unfair resource consumption. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Why limits exist</h2> |
|||||||
| 7 | <p>Limits keep APIs reliable for everyone using the platform.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Rate limits may apply by user, organization, project, API credential, IP address, or endpoint. Exact limits should be documented here as APIs stabilize. |
||||||
| 11 | ||||||||
| 12 | ## Limit dimensions |
|||||||
| 13 | ||||||||
| 14 | - Requests per time window. |
|||||||
| 15 | - Burst capacity. |
|||||||
| 16 | - Endpoint-specific limits. |
|||||||
| 17 | - Project or organization quotas. |
|||||||
| 18 | - Webhook delivery retry limits. |
|||||||
| 19 | ||||||||
| 20 | ## Client behavior |
|||||||
| 21 | ||||||||
| 22 | 1. Respect status codes and retry headers. |
|||||||
| 23 | 2. Use exponential backoff for retries. |
|||||||
| 24 | 3. Cache stable responses where appropriate. |
|||||||
| 25 | 4. Avoid polling when [[Webhooks]] can provide updates. |
|||||||
| 26 | 5. Contact support if a legitimate integration needs higher limits. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Api-Reference">API Reference</a> |
|||||||
| 30 | <a class="docs-card" href="/Webhooks">Webhooks</a> |
|||||||
| 31 | <a class="docs-card" href="/SDKs">SDKs</a> |
|||||||
| 32 | <a class="docs-card" href="/Security">Security</a> |
|||||||
| 33 | </div> |
|||||||