Docs menu
i API endpoint
i sections API
Lists the 45 i sections accepted by `inews-headlines`, from `home` and `news` to `football`, `money` and `relationships`. Each entry has a `slug`, display `name` and `url`. `home` is the site-wide listing, and low-volume sections such as `golf` or `comedy` may hold only one or two items.
GETapiKey1 credit/requestipublicnews.sectionsResponseDoc
i/inews/sectionsEndpoint facts
- Method
- GET
- API path
- /inews/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- i
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns every section slug accepted by inews-headlines, with its display name and public RSS feed URL. No parameters.
The 45 slugs are: home, news, world, technology, politics, science, business, education, environment, health, media, housing, crime, sport, tennis, football, rugby-union, golf, cricket, boxing, olympics, rugby-league, opinion, editor, columnists, comment, culture, television, music, film, books, arts, radio, comedy, inews-lifestyle, money, property-and-mortgages, saving-and-banking, pensions-and-retirement, investing, small-business, travel, food-and-drink, homes-and-gardens, relationships.
home is the site-wide feed (the same stories as inews-news). Parent sections such as news, sport, opinion, culture, inews-lifestyle (labelled "Lifestyle"), and money aggregate stories filed directly under that top-level or mid-level category, separately from their own child sections. A handful of sections (for example business, golf, olympics, comment, editor, comedy) are low-volume and can carry only one or two items at a time.
Sampled response
- Request, 14 Oct 2026
- GET /inews/sections
- Items in sections
- 45
- Fields filled in every checked item
- 3
| Field | Filled in, of 45 checked | Values in the sample |
|---|---|---|
| slug | 45 | |
| name | 45 | “Home” and 44 other values |
| url | 45 | inews.co.uk |
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/inews/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "home",
"name": "Home",
"url": "https://inews.co.uk/feed"
},
{
"slug": "world",
"name": "World",
"url": "https://inews.co.uk/category/news/world/feed"
}
]
}
}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/inews/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"