Rate limits

The etg24 platform is architected for high-volume enterprise operations, including full-portfolio onboarding and mass document ingestion. The platform does not currently enforce rigid, hardcoded per-endpoint request caps that terminate requests abruptly.

Instead, capacity is actively monitored and elastically scaled so that well-architected integrations run smoothly without encountering artificial throughput barriers.

Designing resilient clients

To ensure long-term stability and guard against potential traffic spikes, your client implementations should follow industry best practices:

• Handle HTTP 429 Too Many Requests: Respect 429 status codes and honor the Retry-After header if present.
• Implement exponential backoff with jitter: When retrying transient network errors or rate warnings, introduce randomized jitter to avoid thundering-herd problems.
• Enforce cursor pagination: Always consume large lists via paginated endpoints with reasonable batch sizes (limit=50 or limit=100) rather than requesting unbounded datasets.
• Connection pooling: Reuse HTTP connections via keep-alive to reduce TLS handshake overhead.

High-volume migrations & bulk imports

If you are planning an intensive initial portfolio migration, an automated backfill, or high-frequency telemetry streaming:

• Contact our engineering team ahead of time.
• We will review your projected concurrency and throughput requirements.
• We can provision dedicated scaling thresholds to ensure your migration completes without bottlenecking daily operational traffic.