Ramp Rate-Limit and Timeout Control

Overview

Coordinate all workers that share an egress IP, because independent per-process retries can amplify a rolling-window breach. Preserve idempotency and reconcile ambiguous writes before retry.

Prerequisites

• Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary.
• Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation.
• Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved.
• Prepare approved secret storage and a sanitized evidence location.

Current Contract

• Ramp currently documents a default limit of 200 requests per rolling 10-second window per source IP.
• A 429 means pause and back off; immediate retries worsen contention.
• Requests taking longer than 60 seconds terminate with 504, so large reads should be paginated and work units reduced.
• Ramp recommends exponential backoff; actual throughput is lower than theoretical throughput and endpoint constraints still apply.