Houston Chronicle API Documentation

First request

Endpoint

GET /houston-chronicle/sections

Cost

1 credit/request

curl "https://api.crawlora.net/api/v1/houston-chronicle/sections" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use Houston Chronicle endpoints

Houston Chronicle is Hearst's Houston newsroom, spanning local and Texas reporting, weather, politics, business, sports, entertainment, food, opinion, and investigations. A live /houston-chronicle/sections response on 2026-10-14 contained 35 section records; refresh it before scheduling because publisher feeds change. Use the exact returned section slugs to monitor a Houston desk, and keep a section value with every headline batch. The verified section set comes from first-party page navigation and content-bearing pages, rather than guessed URL prefixes. Canonical story and author URLs can be passed to their dedicated routes. Hearst pages sometimes return a client challenge; the API reports that upstream failure rather than treating it as an empty feed. RSS candidates were not usable, so collection uses publisher pages and sitemaps. Article and profile access can vary. Use the endpoint cards for this integration's accepted inputs.

1. Step 1

   Use exact slugs from first-party navigation

   A live /houston-chronicle/sections response on 2026-10-14 contained 35 section records; refresh it before scheduling because publisher feeds change. Use the exact returned section slugs to monitor a Houston desk, and keep a section value with every headline batch. The verified section set comes from first-party page navigation and content-bearing pages, rather than guessed URL prefixes. Canonical story and author URLs can be passed to their dedicated routes.

2. Step 2

   Log Hearst challenges as access outcomes

   When a call returns a Hearst client challenge, record it as an upstream access outcome and retry according to your collection policy; it is not an empty section. Use observed section slugs and canonical article/profile URLs, while allowing for page-level access differences.

3. Step 3

   Keep the slug with each headline batch

   When a call returns a Hearst client challenge, record it as an upstream access outcome and retry according to your collection policy; it is not an empty section. Use observed section slugs and canonical article/profile URLs, while allowing for page-level access differences. Pass only a value returned by /houstonchronicle/sections and accepted by /houstonchronicle/headlines; preserve the selected desk with its results.

4. Step 4

   Allow page-level access differences

   Hearst pages sometimes return a client challenge; the API reports that upstream failure rather than treating it as an empty feed. RSS candidates were not usable, so collection uses publisher pages and sitemaps. Article and profile access can vary. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.

5. Step 5

   Resolve profiles from canonical URLs

   Use the exact returned section slugs to monitor a Houston desk, and keep a section value with every headline batch. The verified section set comes from first-party page navigation and content-bearing pages, rather than guessed URL prefixes. Canonical story and author URLs can be passed to their dedicated routes. Hearst pages sometimes return a client challenge; the API reports that upstream failure rather than treating it as an empty feed. RSS candidates were not usable, so collection uses publisher pages and sitemaps. Article and profile access can vary.

Other Media & Streaming APIs