Docs menu
Houston Chronicle API endpoint
Houston Chronicle sections API
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.
GETapiKey1 credit/requestHouston Chroniclepublicnews.sectionsResponseDoc
Houston Chronicle/houston-chronicle/sectionsEndpoint facts
- Method
- GET
- API path
- /houston-chronicle/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Houston Chronicle
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the complete live-verified public editorial navigation inventory accepted by houston-chronicle-headlines. The 35 slugs are 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, and visuals. Newsletter signup pages, the duplicate Recipes link, third-party classifieds/store pages, puzzles, podcasts, and project/tool links are not editorial article sections.
Workflow check
Start from the checked request: GET /houston-chronicle/sections. Live check on 2026-10-14: 35 sections returned. Fields present in every checked item: slug, name, url.
Use a returned section value with Get Houston Chronicle section headlines.
Live monitoring
- Monitored request
- GET /houston-chronicle/sections
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 0.08 s
Sampled response
- Request, 14 Oct 2026
- GET /houston-chronicle/sections
- Items in sections
- 35
- Fields filled in every checked item
- 3
| Field | Filled in, of 35 checked | Values in the sample |
|---|---|---|
| slug | 35 | |
| name | 35 | “Local News” and 34 other values |
| url | 35 | 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/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"sections": [
{
"slug": "news-houston-texas",
"name": "Local News",
"url": "https://www.houstonchronicle.com/news/houston-texas/"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.sectionsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.SectionsResponse | No | ||||
| data.sections | array | No | ||||
| data.sections[].name | string | No | ||||
| data.sections[].slug | string | No | ||||
| data.sections[].url | string | No |
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/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"