DuckDuckGo Shopping API

Endpoint facts

Method

GET

API path

/duckduckgo/shopping

Auth

apiKey

Credits

3 credits/request

Platform

DuckDuckGo Search

Response schema

#/definitions/duckduckgo.shoppingResponseDoc

Overview

Returns normalized DuckDuckGo shopping results for a query string: title, brand, merchant, description, price, rating, and review count, plus total page count. DuckDuckGo's shopping vertical is ad-funded, syndicated product listings, not organic content; every product link is wrapped in an ad-click-tracking redirect with no clean destination to unwrap, so no destination URL is returned. DuckDuckGo's own pagination token for this vertical is an opaque per-response blob rather than a plain page offset, so only the first page is supported. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- DuckDuckGo's shopping vertical is ad-funded, syndicated product listings (Bing Product Ads), not organic content. Every product link DuckDuckGo returns is wrapped in an ad-click-tracking redirect carrying opaque campaign/session metadata with no clean destination to unwrap — so, like this API's Google Shopping endpoint, no destination URL is returned. - Only the first page is supported. DuckDuckGo's own pagination token for this vertical is an opaque per-response blob rather than a plain page offset, unlike this API's other DuckDuckGo endpoints. `page_info` reports the total page count DuckDuckGo has available, for context. - A blocked or CAPTCHA-served response returns `503`. - No results returns `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "running shoes", "results": [ { "position": 1, "title": "On Running Cloud 6 Sneakers", "brand": "On", "merchant": "www.example.com", "description": "Lightweight running shoe with CloudTec cushioning.", "price": "$139.99", "low_price": "$119.99", "rating": 4.5, "review_count": 128, "image": "https://example.com/shoe.jpg" } ], "page_info": { "page": 1, "total_pages": 16 } } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related