Rate Limits

Rate Limits protect AeThex services from overload, abuse, accidental loops, and unfair resource consumption.

Why limits exist

Limits keep APIs reliable for everyone using the platform.

Rate limits may apply by user, organization, project, API credential, IP address, or endpoint. Exact limits should be documented here as APIs stabilize.

Limit dimensions

  • Requests per time window.
  • Burst capacity.
  • Endpoint-specific limits.
  • Project or organization quotas.
  • Webhook delivery retry limits.

Client behavior

  1. Respect status codes and retry headers.
  2. Use exponential backoff for retries.
  3. Cache stable responses where appropriate.
  4. Avoid polling when Webhooks can provide updates.
  5. Contact support if a legitimate integration needs higher limits.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9