DuckDuckGo Search API — Authentication — FetchLayer Docs
Documentation menu
FetchLayer FetchLayer API

Authentication

All requests use your FetchLayer API key as a Bearer token. No DuckDuckGo account and no search API agreement are required.

Sending requests

bash
curl -X POST https://api.fetchlayer.dev/duckduckgo/search \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{"query":"open source crm","limit":10}'

Keep your key secret

Only use API keys in server-side code and rotate a key immediately if it is exposed.

Every route is a POST

All seven DuckDuckGo endpoints take a JSON body over POST. There is no query-string route, so the key never travels in a URL. Unrecognised body fields are rejected with a 400 naming the field, so a typo fails loudly instead of returning unfiltered results.

Authentication errors

A missing or invalid key returns HTTP 401.

json
{
  "error": "Invalid API key"
}