Docs menu
Houston Chronicle API endpoint
Houston Chronicle top stories API
Returns current public Houston Chronicle homepage stories. Publisher premium markers are preserved on article responses.
GETapiKey1 credit/requestHouston Chroniclepublicnews.newsResponseDoc
Houston Chronicle/houston-chronicle/newsEndpoint facts
- Method
- GET
- API path
- /houston-chronicle/news
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Houston Chronicle
- Response schema
- #/definitions/publicnews.newsResponseDoc
How this endpoint behaves
Returns headline cards currently visible on the public Houston Chronicle homepage. RSS feeds returned no usable items, so this endpoint reads the public homepage instead. It does not require account cookies or login state.
Workflow check
Start from the checked request: GET /houston-chronicle/news. Live check on 2026-10-14: 16 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/news
- Checks passed, 7 days to 14 Oct 2026
- 98.4%
- Median response time
- 3.20 s
Sampled response
- Request, 14 Oct 2026
- GET /houston-chronicle/news
- Items in items
- 16
- Fields filled in every checked item
- 2
| Field | Filled in, of 16 checked | Values in the sample |
|---|---|---|
| title | 16 | median 76 characters |
| url | 16 | houstonchronicle.com |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/houston-chronicle/news" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"items": [
{
"title": "Example Houston story",
"url": "https://www.houstonchronicle.com/news/houston-texas/article/example-story-22400001.php",
"summary": "Example public summary.",
"published_at": "2026-09-28T17:00:00Z"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.newsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.NewsResponse | No | ||||
| data.items | array | No | ||||
| data.items[].author | string | No | ||||
| data.items[].image_url | string | No | ||||
| data.items[].published_at | string | No | ||||
| data.items[].summary | string | No | ||||
| data.items[].title | string | No | ||||
| data.items[].type | string | No | ||||
| data.items[].url | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 429 | Too Many Requests | #/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/news" \
-H "x-api-key: $CRAWLORA_API_KEY"