Proxy Port: Targeting and Sessions in the Username
The FourA proxy port reads network, country and sticky sessions from the username, and a typo gets a 400 naming the valid keys. Here's the whole grammar.
The FourA proxy port reads network, country and sticky sessions from the username, and a typo gets a 400 naming the valid keys. Here's the whole grammar.
Name the browser, OS and version each request presents, from a public catalogue of 79 measured profiles. When a site refuses one, rotation now moves it.
The Auto endpoint picks Single, Proxy Finder, or Browser for each request, handles pages that check who is asking, and returns a session your next call can reuse.
Declare which responses count as success using validate rules. Non-200 responses you accept now bill correctly and show as success in your Activity feed.
We shipped a Playground inside the Dashboard. Pick an endpoint, fill the fields, hit Send, copy the curl. Three endpoints, one cookie jar, every header.
4.2 million requests in 24 hours. Average 774 ms, down from 2.5 seconds the week before. Here's what changed in the request path, with real percentiles.
One flag flips three switches: real browser headers, a matching connection signature, and auto-decompression for gzip and brotli. Here's what it does and why.
FourA's API now supports configurable redirect limits and raw binary responses. Two options that change how you handle real-world scraping edge cases.
Over 70% of modern websites need JavaScript to render their content. Here's how FourA browser tasks get you the full page when HTTP requests return empty.
Request volume, success rates, response times, cost breakdowns per domain: the FourA analytics dashboard shows what's working and where to optimize next.