Ramp API Throughput and Sync Performance

Overview

Measure first, then tune by endpoint and object lifecycle. Maximize useful work per request while staying below shared limits and keeping checkpoints at durable commit boundaries.

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's default rate limit is 200 requests per rolling 10-second window per source IP, subject to current documentation and approved increases.
• API requests exceeding 60 seconds return 504; pagination and smaller work units are the primary controls for large reads.
• Most list endpoints support cursor-style pagination, but page sizes and incremental filters are endpoint-specific.
• Accounting batch endpoints may have explicit item caps and all-or-nothing behavior; current schema controls each batch.