媒体与流媒体5 active endpointsapiKey

Published 2026年10月15日

Houston Chronicle API

Hearst's Houston newsroom, spanning local and Texas reporting, weather, politics, business, sports, entertainment, food, opinion, and investigations. 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.

Collect Hearst's Houston newsroom, spanning local and Texas reporting, weather, politics, business, sports, entertainment, food, opinion, and investigations.

View docs Open Playground

Endpoint families

Documented params

Examples

Live catalog snapshot

Houston Chronicle coverage

Active endpoints

Methods

GET

Required params

Schema refs

Article1

Author1

Headlines1

News1

{
  "platform": "Houston Chronicle",
  "endpoint": "houston-chronicle-sections",
  "method": "GET",
  "path": "/houston-chronicle/sections",
  "auth": "apiKey"
}

Use cases

Workflows that fit Houston Chronicle

Collect Hearst's Houston newsroom, spanning local and Texas reporting, weather, politics, business, sports, entertainment, food, opinion, and investigations.

Monitor Hearst's Houston newsroom

Use Houston Chronicle endpoints to turn monitor hearst's houston newsroom into repeatable API requests with documented inputs and JSON responses.

Separate Houston Chronicle feed records from article or profile follow-up

Use Houston Chronicle endpoints to turn separate houston chronicle feed records from article or profile follow-up into repeatable API requests with documented inputs and JSON responses.

Preserve source URLs, dates, and access outcomes for review

Use Houston Chronicle endpoints to turn preserve source urls, dates, and access outcomes for review into repeatable API requests with documented inputs and JSON responses.

Managed execution

How Crawlora handles this platform

Every figure below is read from the live Houston Chronicle endpoint catalog — 5 endpoints, 8 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.

Documented endpoint coverage

5 documented Houston Chronicle endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.

Published request surface

8 request parameters are documented across those Houston Chronicle endpoints, 8 of them required — the full input contract is public before you write any integration code.

Known response shape

5 of the 5 Houston Chronicle endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.

Documented failure modes

Houston Chronicle endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.

Agent-callable MCP tools

5 hosted MCP tools back the Houston Chronicle endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.

Returns every live-verified public editorial section accepted by the Houston Chronicle headlines endpoint. Newsletter, games, audio-only, external marketplace and interactive project/tool links are excluded.

MCP tool houston_chronicle_sections

x-api-key:header

Open in Playground

Integration preview

Get Houston Chronicle sections

curl -X GET "https://api.crawlora.net/api/v1/houston-chronicle/sections" \
  -H "x-api-key: <api-key>"

Primary auth: apiKey
Path params: 0
Query/body inputs: 1

Choose a documented endpoint.

Send the expected auth header.

Receive structured JSON data.

Test the same route in Playground.

Related APIs

More 媒体与流媒体 coverage

Media & Streaming

FUSSBALL.DE

Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.

Media & Streaming

Sportskeeda

Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.

Media & Streaming

JustWatch

Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.

How to scrape Houston Chronicle

Extract Houston Chronicle data in 5 steps

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. Publisher reference: https://www.houstonchronicle.com/

Step 1
Refresh Houston Chronicle's editorial inventory
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.
Step 2
Plan around Houston Chronicle's source-specific constraints
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.
Step 3
Carry Houston Chronicle section context into each headline pull
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.
Step 4
Check Houston Chronicle article access before using body text
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.
Step 5
Use Houston Chronicle's contributor route for its documented purpose
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.

FAQ

Scraping Houston Chronicle: common questions

How should I scope a Houston Chronicle headline pull?

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.

What should I preserve when using Houston Chronicle's article route?

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.

What should a collector avoid assuming about Houston Chronicle?

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.

Test Houston Chronicle endpoints against the same catalog used by Docs.

Read docs Create account

Houston Chronicle API

Collect Hearst's Houston newsroom, spanning local and Texas reporting, weather, politics, business, sports, entertainment, food, opinion, and investigations.

Extract Houston Chronicle data in 5 steps

Houston Chronicle API

Houston Chronicle coverage

Workflows that fit Houston Chronicle

Monitor Hearst's Houston newsroom

Separate Houston Chronicle feed records from article or profile follow-up

Preserve source URLs, dates, and access outcomes for review

How Crawlora handles this platform

Documented endpoint coverage

Published request surface

Known response shape

Documented failure modes

Agent-callable MCP tools

Know what the API can collect before integrating

Article

Author

Headlines

News

Sections