Daily Kos API Documentation

First request

Endpoint

GET /dailykos/sections

Cost

1 credit/request

curl "https://api.crawlora.net/api/v1/dailykos/sections" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use Daily Kos endpoints

Daily Kos is a progressive political publication and reader community with staff reporting and 24 verified WordPress editorial categories. A live /dailykos/sections response on 2026-10-14 contained 24 category records; refresh it before scheduling because publisher feeds change. Fetch the returned category slugs before selecting a desk, then use category headlines to monitor politics, elections, policy, and other editorial beats. For a story body, pass a canonical staff-written story URL from the feed; do not treat reader diaries or the enormous changing tag space as supported filters. Article extraction is limited to supported staff story paths. There is no author route. The category list is a verified set; arbitrary tags and search are not section parameters. Use the endpoint cards for this integration's accepted inputs.

1. Step 1

   Discover the category list first

   A live /dailykos/sections response on 2026-10-14 contained 24 category records; refresh it before scheduling because publisher feeds change. Fetch the returned category slugs before selecting a desk, then use category headlines to monitor politics, elections, policy, and other editorial beats. For a story body, pass a canonical staff-written story URL from the feed; do not treat reader diaries or the enormous changing tag space as supported filters.

2. Step 2

   Build jobs from exact category slugs, not tags

   The 24 WordPress categories provide a bounded editorial taxonomy; discover them before building recurring jobs and use the exact category slug. Staff story URLs can be sent to article extraction, while reader diaries and arbitrary tags fall outside the validated staff-story contract.

3. Step 3

   Pass only discovered WordPress categories

   The 24 WordPress categories provide a bounded editorial taxonomy; discover them before building recurring jobs and use the exact category slug. Staff story URLs can be sent to article extraction, while reader diaries and arbitrary tags fall outside the validated staff-story contract. Pass only a value returned by /dailykos/sections and accepted by /dailykos/headlines; preserve the selected desk with its results.

4. Step 4

   Send supported staff-story URLs to extraction

   Article extraction is limited to supported staff story paths. There is no author route. The category list is a verified set; arbitrary tags and search are not section parameters. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.

Other Media & Streaming APIs