FourA Digest — Oct 30 to Nov 6, 2026

FourA shipped a Proxy Finder update that lets premium exits be targeted by region, city, network (AS number) and device type, with exitLifetimeMin holding the same address for 3 to 1,440 minutes, the company said in its Oct 30 to Nov 6, 2026 digest. The new fields require exitClass "premium" and a plan with geo targeting, and requests that exhaust premium traffic are refused with a 403 carrying X-FourA-Limit: plan_limit_premium. FourA also removed the exitCountry field from /api/browser, which now derives the timezone from the proxy ID alone, and fixed Dashboard searchable dropdowns on iPhone.

Highlights Need an address in Sofia that stays the same for a quarter of an hour? Proxy Finder can give you one now. Premium exits take a region, a city, a network, a device type and a lifetime, and the proxy ID you get back carries the place to Single and Browser. In the Dashboard, searchable fields behave on a phone, a new account's Overview stops shifting while it loads, and Auto runs in the playground land in History. Everything below is live, and most of it's on the changelog https://updates.foura.ai as well. What's New Premium exits by region, city, network and device Some targets care where you're standing, not only which country you're in. A price that changes by city. A store finder. A site that treats a mobile carrier differently from a home connection. Proxy Finder now takes five more fields on premium exits: - exitState , exitCity and exitAsn pick the region, the city or the network by AS number the exit leaves from. They need exactly one country in exitCountries . - exitOs picks the kind of device the address belongs to: windows , android , ios or mac . - exitLifetimeMin keeps the same address for anywhere from 3 to 1,440 minutes. Any of them needs exitClass: "premium" and sends the request through premium exits only, since the standard pool can't honour a place. Region, city, network and device also need a plan with geo targeting. And if your premium traffic is spent, the request is refused with a 403 carrying X-FourA-Limit: plan limit premium , so it never leaves from somewhere you didn't ask for. The useful part comes after the first call. The proxy ID in the answer keeps the place, so a follow-up on Single or Browser needs that ID and nothing beside it: python import requests H = {"X-API-Key": "pk live ..."} r = requests.post "https://api.foura.ai/api/proxy", headers=H, json={ "exitClass": "premium", "exitCountries": "BG" , "exitCity": "sofia", "exitLifetimeMin": 15, "request": {"method": "GET", "url": "https://example.com/"}, }, .json Same city, same address, for the lifetime you asked for page = requests.post "https://api.foura.ai/api/single", headers=H, json={"url": "https://example.com/stores", "proxy": r "proxy" }, .json These are the words the proxy port https://foura.ai/proxy already takes for state , city , asn and os , so targeting you've tuned on the port carries straight over. The exit location reference https://foura.ai/docs/api/endpoints exit-location lists every rule, and the Proxy tab of the Dashboard playground https://foura.ai/docs/dashboard/playground has an Exit location group, so you can try a place before you write any code. One more change rides along. A premium exit given a country list now stays inside it, and exitCountry in the response names the country it left from, the same as for the standard pool. Browser reads the country from the proxy ID A page can compare the browser's timezone with the country of the address it sees, and a mismatch is one of the cheapest bot signals around. Browser lines the two up for you. It now takes the timezone from the proxy ID alone, so the exitCountry field on /api/browser is gone. A request that still sends it keeps working; the field is simply ignored. Dashboard on a phone, and on day one Searchable dropdowns in the Dashboard work properly on a phone now. Tapping one doesn't zoom the page on an iPhone, a tap anywhere else closes the list, opening it doesn't pull up the keyboard, and the list fits in the space the keyboard leaves. Tapping the small i beside a label no longer opens the field under it. A new account's Overview loads its setup guide together with the rest of the page. So the filters stay where you first see them instead of sliding down a moment later. On an account with no API traffic yet, only the API panels carry the Sample label if you only use the proxy port, your Proxy panels show your real numbers with no label at all . Auto runs in History Auto runs in the Dashboard playground now land in History beside Single, Proxy and Browser, and you can save an Auto request as a preset. That's worth having because Auto is a path finder, not the production route: it tells you which way into a site works, and the session it hands back is what you replay on Single, Proxy Finder or Browser at volume. With the run in History you can come back to the route it found, and the Carry button moves its user agent and proxy ID onto the other tabs. Invoices for plans billed after the month If your plan is billed after the month, its invoice now goes out on its own when each billing month ends, due seven days later. The email carries the PDF, our bank details and the invoice number to use as your payment reference. The same invoice sits under Invoices in Billing. Under the Hood Browser servers now clear out their own working memory. If one still runs short, it leaves rotation until it recovers, and your requests go to servers that can finish them. Our API servers got the same kind of care: their health checks no longer wait on anything that can stall, so a server that can't do its job says so quickly and its traffic moves to the others. A proxy ID used to mean an exit. Now it can mean a city, a network and a quarter of an hour.