Upstreams

SerpApi

Search engine results with the api_key injected for you

View as Markdown

Proxies SerpApi’s search endpoint, injecting the secret api_key query parameter.

GET /serpapi   → https://serpapi.com/search?api_key=<secret>&<your query>

GET only — SerpApi documents no POST for search. Every control travels in the query string and is forwarded verbatim: engine (SerpApi defaults it to google), q, location, output (json default / html for the raw page), and so on. The gateway injects and defaults nothing beyond the key — your call behaves exactly as if it hit SerpApi directly.

What the gateway injects and strips

  • api_key is injected as the first query parameter.
  • A client-supplied api_key query param is dropped (in any encoding), so the injected key can’t be overridden.
  • The Authorization header is stripped before forwarding — SerpApi has no use for your gateway token.

Examples

$curl "$GATEWAY/serpapi?engine=google&q=coffee" \
>  -H "Authorization: Bearer $TOKEN"

The response is SerpApi’s JSON (or HTML with output=html), returned unchanged. For the full parameter set per engine, see SerpApi’s documentation.