Errors and Rate Limits

Use this guide to implement resilient client behavior for failures, throttling, and audit-safe operations.

Common HTTP Status Codes

Code	Meaning
400	Invalid input payload or request format.
401	Authentication required or missing organization context.
403	Caller is authenticated but lacks required permissions.
404	Route is disabled, unavailable, or resource not found.
429	Request exceeded rate limits for this route class.
500	Unexpected server failure. Retry with backoff.

Rate Limit Headers

X-RateLimit-Limit
X-RateLimit-Remaining
X-RateLimit-Reset
Retry-After (present when throttled)

Retry Pattern

if (response.status === 429) {
  const retryAfterSeconds = Number(response.headers.get('Retry-After') ?? '1');
  await wait(retryAfterSeconds * 1000);
  // Retry with capped exponential backoff and idempotent request design
}

Retention and Audit Downloads

Treat all exported logs and evidence files as controlled audit records. Keep retention decisions aligned with your compliance policy and verify file integrity checks when evidence is moved between systems.

Operational checklist

Store exported records in an access-controlled location.
Track export job ids and request ids in change tickets.
Document retention windows in your customer runbook.

Need Endpoint-Specific Details?

Continue to API Reference for path-level coverage and request/response examples.

Open API Reference