Tools

Linkup

The Linkup Search API
View as Markdown

Proxies Linkup’s Search API, with Linkup’s /v1 base folded into the route:

POST /linkup/search   → https://api.linkup.so/v1/search

POST only. Every control (q, depth, outputType, …) travels in the JSON body and is forwarded unchanged.

What the gateway injects and strips

Linkup authenticates with the Authorization: Bearer header — the same header you use for your gateway token. So the gateway overwrites it with the injected Linkup key:

  • The Authorization header is overwritten with the secret Linkup key. Your gateway token is consumed by the gateway and never reaches Linkup.
  • Linkup has no query-param spelling of the key, so nothing is dropped from the query string.

Example

$curl -X POST "$GATEWAY/linkup/search" \
>  -H "Authorization: Bearer $TOKEN" \
>  -H "Content-Type: application/json" \
>  -d '{"q": "latest cloudflare workers features", "depth": "standard", "outputType": "searchResults"}'

The response is Linkup’s JSON, returned unchanged. For request and response fields, follow Linkup’s documentation — the gateway does not alter them.