Docs menu
Houston Chronicle API endpoint
Houston Chronicle section headlines API
Returns 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.
GETapiKey1 credit/requestHouston Chroniclepublicnews.headlinesResponseDoc
Houston Chronicle/houston-chronicle/headlinesEndpoint facts
- Method
- GET
- API path
- /houston-chronicle/headlines
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Houston Chronicle
- Execution
- Managed browser rendering where the target needs it
- Response schema
- #/definitions/publicnews.headlinesResponseDoc
How this endpoint behaves
Query parameter: section is required and must be one of news-houston-texas, news-houston-texas-trending, neighborhood, news-houston-texas-education, news-houston-texas-environment, health, news-houston-weather, politics, politics-houston, politics-texas, politics-us-world, business, business-energy, business-real-estate, business-tech, sports, sports-texans, sports-astros, sports-rockets, sports-college, sports-high-school, sports-dynamo, entertainment, lifestyle, food-restaurants, food-restaurants-reviews, food-restaurants-bbq, opinion, opinion-editorials, opinion-letters, opinion-columnists, news-interactives, news-investigations, la-voz, or visuals. Any other value returns a 400 invalid-parameter error. Pages that return Hearst's Client Challenge are retried through configured render backends; access controls are not bypassed.
Workflow check
Start from the checked request: GET /houston-chronicle/headlines?section=sports-texans. Live check on 2026-10-14: 9 items returned. Fields present in every checked item: title, url.
Resolve a returned canonical story URL with Get Houston Chronicle article content.
Live monitoring
- Monitored request
- GET /houston-chronicle/headlines?section=sports-texans
- Checks passed, 7 days to 14 Oct 2026
- 99.7%
- Median response time
- 2.75 s
Sampled response
- Request, 14 Oct 2026
- GET /houston-chronicle/headlines?section=sports-texans
- Items in items
- 9
- Fields filled in every checked item
- 2
| Field | Filled in, of 9 checked | Values in the sample |
|---|---|---|
| title | 9 | median 76 characters |
| url | 9 | houstonchronicle.com |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| section | string | Yes | Houston Chronicle public section slug Allowed values: news-houston-texas, news-houston-texas-trending, neighborhood, news-houston-texas-education, news-houston-texas-environment, health, news-houston-weather, politics, politics-houston, politics-texas, politics-us-world, business, business-energy, business-real-estate, business-tech, sports, sports-texans, sports-astros, sports-rockets, sports-college, sports-high-school, sports-dynamo, entertainment, lifestyle, food-restaurants, food-restaurants-reviews, food-restaurants-bbq, opinion, opinion-editorials, opinion-letters, opinion-columnists, news-interactives, news-investigations, la-voz, visuals. | sports-texans | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/houston-chronicle/headlines?section=sports-texans" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"section": "news-houston-texas",
"items": [
{
"title": "Example Houston story",
"url": "https://www.houstonchronicle.com/news/houston-texas/article/example-story-22400001.php",
"summary": "Example public summary."
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.headlinesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.HeadlinesResponse | No | ||||
| data.items | array | No | HeadlineItem record, 7 fields: author, image_url, published_at, summary, title, type, url. Described under Houston Chronicle top stories API. | |||
| data.section | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/houston-chronicle/headlines?section=sports-texans" \
-H "x-api-key: $CRAWLORA_API_KEY"