# A Stripe REST API ingestion job paginates by stopping at the first empty response, burns its rate bu Canonical URL: Domain: Pipeline Design ยท Difficulty: medium ## Problem A Stripe REST API ingestion job paginates by stopping at the first empty response, burns its rate budget in the first five minutes of every run, and lets the OAuth token expire mid-pagination with no refresh. Three Stripe outages a month show up in the pipeline as silent partial loads. The section names four concerns of API ingestion: pagination (cursor-based is the strongest), rate limits (respect Retry-After), auth (refresh before expiry), and reliability (retry with backoff on 429 and 5xx). Add the rate limiter by replacing the API ingest transform with one whose name states cursor-based pagination, a rate-limiter that respects Retry-After, an OAuth refresh policy, and retry-with-backoff on 429 and 5xx. ## Related - [All practice problems](https://datadriven.io/problems) - [Mock interview mode](https://datadriven.io/interview/a-stripe-rest-api-ingestion-job-paginates-by-stopping-at-the-22946867) - [System Design Interview Questions](https://datadriven.io/data-engineering-system-design) - [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep) - [Daily Challenge](https://datadriven.io/daily) --- Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.