Docs menu
DailyWire API endpoint
Daily Wire sections API
Lists the Daily Wire content verticals that `dailywire-headlines` accepts, such as `news`, `opinion`, `analysis`, `entertainment`, `upstream` and `sports`. Each entry has a `slug`, `name` and `url`. Sampled on 2026-09-24, so the list may not be exhaustive.
GETapiKey1 credit/requestDailyWirepublicnews.sectionsResponseDoc
DailyWire/dailywire/sectionsEndpoint facts
- Method
- GET
- API path
- /dailywire/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- DailyWire
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the live-sampled (2026-09-24) public Daily Wire content-vertical inventory used by dailywire-headlines's section parameter: news, opinion, dw-opinion, analysis, news-and-commentary, news-and-analysis, exclusive, entertainment, original, upstream, sports, mi-x-dw.
Daily Wire has no real per-category hub page (/politics, /sports, /opinion, etc. all return HTTP 200 but never resolve to real content) and no public taxonomy-listing API (/wp-json/ is swallowed by the same catch-all route as every other unknown path). This list is instead sampled from the WordPress category label the site's own homepage feed and several staff/contributor author pages attach to each article, and is not guaranteed exhaustive -- each additional author page sampled during research turned up at least one previously unseen label.
Sampled response
- Request, 14 Oct 2026
- GET /dailywire/sections
- Items in sections
- 12
- Fields filled in every checked item
- 3
| Field | Filled in, of 12 checked | Values in the sample |
|---|---|---|
| slug | 12 | |
| name | 12 | “News” and 11 other values |
| url | 12 | dailywire.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/dailywire/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "news",
"name": "News",
"url": "https://www.dailywire.com/"
},
{
"slug": "sports",
"name": "Sports",
"url": "https://www.dailywire.com/"
}
]
}
}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/dailywire/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"