Rate limits

Some Igdrasil endpoints and upstream integrations can return 429 responses. Treat them as temporary failures.

Client behavior

• Preserve the X-Request-Id response header.
• Honor Retry-After when it is present.
• Use exponential backoff with jitter for retryable reads.
• Avoid retrying writes unless the endpoint documents an idempotency key or your client can prove the operation was not applied.
• Reduce page size or request frequency if list endpoints repeatedly hit limits.

Upstream providers

Integration endpoints may be rate-limited by the connected provider, not only by Igdrasil. In those cases, retry timing should follow the provider-backed endpoint response.