<?xml version="1.0" encoding="UTF-8"?>
<response><data><post><id>20</id><slug>when-to-use-an-api-instead-of-scraping-20</slug><title>When to use an API instead of scraping</title><excerpt>If a site offers an API for the data you need, scraping its HTML is usually the harder, more fragile and less polite option.</excerpt><seriesName>When to use an API instead of scraping</seriesName><seriesPart>1</seriesPart><sections><item><heading>Introduction</heading><paragraphs><item>If a site offers an API for the data you need, scraping its HTML is usually the harder, more fragile and less polite option.</item></paragraphs></item><item><heading>Putting it into practice</heading><paragraphs><item>Be careful with relative URLs. Resolve every link against the page it came from, not against the site root, or you will request pages that do not exist.</item><item>Character encodings still cause trouble. Decode responses using the charset the server declares, and normalise text before comparing or storing it.</item></paragraphs></item><item><heading>Common pitfalls</heading><paragraphs><item>Store raw responses alongside parsed output while you are developing. When a parser breaks, you can replay the saved HTML instead of hitting the site again.</item><item>Treat HTTP 429 responses as a signal, not an obstacle. Read the Retry-After header, back off, and resume at a slower pace.</item></paragraphs></item><item><heading>Key takeaway</heading><paragraphs><item>Check for a documented API, a data export or a feed first. Scrape only when none exists, and read the terms of service either way.</item></paragraphs></item></sections><authorId>11</authorId><authorName>Oliver Kim</authorName><authorSlug>oliver-kim</authorSlug><category>Ethics &amp; Law</category><tags><item>scrapy</item><item>ethics</item><item>javascript</item></tags><publishedAt>2024-10-26T00:00:00.000Z</publishedAt><wordCount>146</wordCount><readingTimeMinutes>2</readingTimeMinutes></post></data></response>
