DuckDuckGo Videos Scraper

Collect rich public video-search records from DuckDuckGo using its structured video response. The Actor supports a single query, multiple queries, website filters, pagination, fair batch interleaving, stable deduplication, and optional Residential or custom HTTP proxies.

Inputs

• query or queries: one query or up to 20 queries.
• maxItems and maxItemsPerQuery: total and per-query limits.
• maxPages: pagination limit per query.
• region: DuckDuckGo region such as us-en, uk-en, or wt-wt.
• safeSearch: strict, moderate, or off.
• timeRange: past day, week, or month.
• resolution: high or standard definition.
• duration: short, medium, or long.
• license: Creative Commons or standard YouTube license.
• maxConcurrency, retry, timeout, and proxy controls.

Direct access is the default. An authorized Residential or custom HTTP proxy may be configured before a run. Access gates stop the run without switching routes or sessions. GOOGLE_SERP cannot be used because it supports Google Search and Shopping rather than DuckDuckGo.

Output

Records include stable IDs and positions; title and description; video, embed, and thumbnail URLs; platform video ID; small, medium, large, and motion thumbnails when supplied; duration and numeric duration seconds; channel, uploader, publisher, platform, and provider; numeric view count; normalized and source publication timestamps; query, region, filter, provenance, and scrape metadata.

The Actor maps the documented public fields and omits DuckDuckGo's internal request token. Empty optional fields are omitted instead of emitted as null or empty strings.

Modes

• Single search: provide query.
• Multiple searches: provide queries; results are interleaved so one query cannot consume the full global limit first.
• One item: set maxItems to 1.
• Filtered search: combine the time, resolution, duration, license, region, and Safe Search inputs.
• No results: completes cleanly with an empty dataset.

Results are available in the default Apify dataset and can be downloaded as JSON, CSV, or Excel or consumed through the Apify API.

Bounded preview and run status

The prefilled input requests five records from one page with one query worker, no retries, a 25-second request timeout, and direct access. It reproduces a hash-verified historical input; it does not certify current source availability. Omitted API values retain the documented runtime defaults.

Ordinary temporary failures may retry on the same route and one fixed authorized proxy session. HTTP 401/403/407/429/451, redirects, login or verification pages, and TLS/proxy-authentication failures stop new requests across all query workers. No CAPTCHA is solved and redirects are not followed. Already completed or successfully in-flight result pages are retained.

The OUTPUT key-value record reports SUCCEEDED, NO_RESULTS, PARTIAL, BLOCKED, or FAILED, with completed/failed/skipped query counts and safe failure codes. Partial rows are retained when a later request fails; a partial status does not claim all requested queries or pages succeeded. Empty blocked/failed runs exit unsuccessfully.