{"data":{"id":169,"slug":"rate-limit-headers-explained-part-9-169","title":"Rate limit headers explained, part 9","excerpt":"Part 9 looks at what changes when the same technique has to run every day in production. A well-behaved API tells you how many requests you have left before it starts saying no. Reading those headers…","seriesName":"Rate limit headers explained","seriesPart":9,"sections":[{"heading":"Introduction","paragraphs":["Part 9 looks at what changes when the same technique has to run every day in production. A well-behaved API tells you how many requests you have left before it starts saying no. Reading those headers turns rate limiting from a surprise into a plan."]},{"heading":"Common pitfalls","paragraphs":["Write small, focused tests for your parsers using saved HTML fixtures. They run in milliseconds and catch layout changes long before a full crawl would.","Read the site's terms of service before you start. Many sites welcome automated access within limits and say so explicitly; others ask you to use an API instead.","Treat HTTP 429 responses as a signal, not an obstacle. Read the Retry-After header, back off, and resume at a slower pace."]},{"heading":"What to watch for","paragraphs":["Keep configuration such as base URLs, delays and selectors out of your code. Changing a delay should not require a redeploy.","Pagination comes in several shapes: numbered pages, next links, offsets and opaque cursors. Each has trade-offs, and a robust scraper should detect the end of the result set rather than assuming a fixed number of pages."]},{"heading":"Key takeaway","paragraphs":["Track X-RateLimit-Remaining, slow down as it approaches zero, and when you receive a 429, wait for the number of seconds in Retry-After before trying again."]}],"authorId":5,"authorName":"Chen Patel","authorSlug":"chen-patel","category":"APIs","tags":["python","testing"],"publishedAt":"2025-10-03T00:00:00.000Z","wordCount":202,"readingTimeMinutes":2}}