API Reference
Use Crawlora's Houston Chronicle API endpoints to extract supported public Houston Chronicle data as structured JSON. This documentation covers 5 active endpoints including Get Houston Chronicle article content, Get a Houston Chronicle author profile, Get Houston Chronicle section headlines, Get Houston Chronicle top stories, and related APIs. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as url, section, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
curl -X GET "https://api.crawlora.net/api/v1/houston-chronicle/article" \
-H "x-api-key: $CRAWLORA_API_KEY"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
Houston Chronicle API endpoints/houston-chronicle/articleapiKey2 credits/requestReturns public Houston Chronicle article metadata and the body available in the anonymous response. Premium stories are flagged from the publisher's content-tier and JSON-LD markers; the service does not authenticate or bypass access controls.
Required params: url:query
/houston-chronicle/authorapiKey2 credits/requestReturns an author's public profile and recent story cards from a canonical Houston Chronicle author URL.
Required params: url:query
/houston-chronicle/headlinesapiKey1 credit/requestReturns current public headlines from a verified Houston Chronicle editorial section. Pages that return Hearst's Client Challenge are retried through configured rendering backends; the service does not solve or bypass access controls.
Required params: section:query
/houston-chronicle/newsapiKey1 credit/requestReturns current public Houston Chronicle homepage stories. The public RSS endpoint returned no usable items; this uses the credential-free homepage and preserves publisher premium markers on article responses.
Required params: None
/houston-chronicle/sectionsapiKey1 credit/requestReturns 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.
Required params: None
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Get Houston Chronicle article content | /houston-chronicle/article | GET | 2 credits/request | url:query | View docs | Try endpoint |
| Get a Houston Chronicle author profile | /houston-chronicle/author | GET | 2 credits/request | url:query | View docs | Try endpoint |
| Get Houston Chronicle section headlines | /houston-chronicle/headlines | GET | 1 credit/request | section:query | View docs | Try endpoint |
| Get Houston Chronicle top stories | /houston-chronicle/news | GET | 1 credit/request | None | View docs | Try endpoint |
| Get Houston Chronicle sections | /houston-chronicle/sections | GET | 1 credit/request | None | View docs | Try endpoint |