ScrapingBee mode=auto plus an explicit tier param is a 400

TL;DR: If you need infinite scroll pagination through a scenario, use the standard premium or datacenter proxies: stealthproxy is incompatible with infinitescroll. Do not combine mode=auto with explicit tier parameters like premiumproxy or stealthproxy; the API rejects the combination with a 400. Either let the API auto-select the tier or name one tier explicitly, not both.

ScrapingBee mode=auto plus an explicit tier param is a 400

Fix

1. If you need infinite scroll pagination through a scenario, use the standard premium or datacenter proxies: stealthproxy is incompatible with infinitescroll. Expected: the request routes instead of erroring.

Details

Do not combine mode=auto with explicit tier parameters like premiumproxy or stealthproxy; the API rejects the combination with a 400. Either let the API auto-select the tier or name one tier explicitly, not both. Read a failed request's error body for the parameter name; most 400s are one of these conflicts.

When to use

You hit exactly this: ScrapingBee mode=auto plus an explicit tier param is a 400.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

the tool named in the title.

Edge cases

• Also know that passing wait_for turns JavaScript rendering on even if you did not ask for it, which changes the cost and behavior of the request.

Web (proxlane integrations doc): documents parameter conflicts that return 400s: mode=auto cannot be combined with explicit proxy-tier parameters, and waitfor quietly forces renderjs on. Stealth proxies are incompatible with infinitescroll. Resolved: Do not combine mode=auto with explicit tier parameters like premiumproxy or stealthproxy; the API rejects the combination with a 400. Either let the API auto-select the tier or name one tier explicitly, not both. Also know that passing waitfor turns JavaScript rendering on even if you did not ask for it, which changes the cost and behavior of the request. If you need infinite scroll pagination through a scenario, use the standard premium or datacenter proxies: stealthproxy is incompatible with infinitescroll. Read a failed request's error body for the parameter name; most 400s are one of these conflicts.