ScrapingBee 400s: custom_google required for Google domains, mode=auto conflicts with tier params

TL;DR

Three ScrapingBee 400s that are not your fault the way they look.

Fix

1. Three ScrapingBee 400s that are not your fault the way they look. Expected: you can confirm this matches your situation.

When to use

• You are setting up or using this ScrapingBee 400s feature.
• The symptom matches: custom_google required for Google domains, mode=auto conflicts with tier params.

When NOT to use

• Unrelated ScrapingBee 400s issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against ScrapingBee 400s.

Variant phrasings

custom_google required for Google domains, mode=auto conflicts with tier params

Why it happens

ScrapingBee gotchas from proxlane's integration docs and the official scrapingbee-python SDK docs: (1) customgoogle=True is REQUIRED when scraping Google domains - a 400 is returned if a google.* URL is sent without it, or if it is set on a non-Google URL. (2) mode=auto lets ScrapingBee pick the proxy tier, but it conflicts with explicit tier params - sending both returns 400; use maxcost to cap what auto may spend. (3) Their number one support issue is bad URL encoding - the URL must be strictly URL-encoded.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source: ScrapingBee gotchas from proxlane's integration docs and the official scrapingbee-python SDK docs: (1) customgoogle=True is REQUIRED when scraping Google domains - a 400 is returned if a google.* URL is sent without it, or if it is set on a non-Google URL. (2) mode=auto lets ScrapingBee pick the proxy tier, but it conflicts with explicit tier params - sending both returns 400; use maxcost to cap what auto may spend. (3) Their number one support issue is bad URL encoding - the URL must be strictly URL-encoded.

Verified resolution: Three ScrapingBee 400s that are not your fault the way they look. Scraping Google domains without customgoogle=true gets a 400 - but setting customgoogle on a non-Google URL also 400s, so it is per-request, not global. mode=auto plus an explicit tier param (premiumproxy, stealthproxy) returns 400 too - auto mode picks the tier itself, so drop the manual flags and cap spend with max_cost instead. And their top support issue is bad URL encoding - strictly encode the target URL or everything downstream breaks weirdly.

Source URL: https://github.com/proxlane/proxlane/blob/HEAD/docs/integrations.md