Docs menu
TheJournal.ie API endpoint
TheJournal.ie sections API
Lists the 22 TheJournal.ie sections that the headlines endpoint accepts, verified 2026-09-25: nine category pages such as `irish`, `politics` and `business`, plus topic pages such as `housing`, `courts`, `ukraine` and `gaza`. Each entry has a `slug`, `name` and listing page `url`. Topic pages outside the site navigation are not served.
GETapiKey1 credit/requestTheJournal.iepublicnews.sectionsResponseDoc
TheJournal.ie/thejournal/sectionsEndpoint facts
- Method
- GET
- API path
- /thejournal/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- TheJournal.ie
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the complete section inventory accepted by /api/v1/thejournal/headlines: 22 listing pages that thejournal.ie publishes with live story cards (verified live 2026-09-25): irish, politics, international, business, tech, science, environment, voices, investigates, factcheck, explainer, gaeilge, sport, money-diaries, quiz, climate-change, housing, cost-of-living, road-safety, courts, ukraine, gaza.
Each section includes a stable slug, a display name, and the public listing page url. The first nine are category pages (/<slug>/); the rest are topic pages (/<slug>/news/) linked from the site's own navigation. The site has no per-section feed, so headlines come from these listing pages. The site also has topic pages for other editorial tags that are not listed here; only the navigation-linked set is served.
Sampled response
- Request, 14 Oct 2026
- GET /thejournal/sections
- Items in sections
- 22
- Fields filled in every checked item
- 3
| Field | Filled in, of 22 checked | Values in the sample |
|---|---|---|
| slug | 22 | |
| name | 22 | “Irish News” and 21 other values |
| url | 22 | thejournal.ie |
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/thejournal/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "irish",
"name": "Irish News",
"url": "https://www.thejournal.ie/irish/"
},
{
"slug": "factcheck",
"name": "FactCheck",
"url": "https://www.thejournal.ie/factcheck/news/"
}
]
}
}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/thejournal/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"