Tools

ZenRows

Universal Scraper API calls with the apikey added by the gateway
View as Markdown

Fronts the Universal Scraper API of ZenRows; the gateway fills in the secret apikey parameter on the query string:

GET|POST /zenrows   → https://api.zenrows.com/v1/?apikey=<secret>&<your query>
  • A GET fetches the target URL.
  • A POST is passed on to the target as a POST.

Everything is driven by the query string: the target url plus any ZenRows parameter (premium_proxy, js_render, css_extractor, autoparse, …). What you put there reaches ZenRows exactly as written.

Credential handling

  • apikey goes in ahead of everything you send, so it can’t be swallowed by a target URL with incomplete encoding.
  • An apikey supplied by the client in the query is discarded (any encoding), so nothing can displace the injected key.
  • Authorization is dropped before the request goes upstream — your gateway token is meaningless to ZenRows.

Examples

$curl "$GATEWAY/zenrows?url=https://example.com" \
>  -H "Authorization: Bearer $TOKEN"

ZenRows’ response comes back untouched. Every supported parameter is listed in ZenRows’ documentation.