Enterprise web data platform for large-scale extraction. Integrate KnoxProxy as an external proxy source in Import.io for geo-targeted data collection and higher success rates on protected sites.
In your Import.io dashboard, navigate to Settings > Proxy Configuration under your account or workspace settings.
Select "Add External Proxy" and enter KnoxProxy connection details.
Proxy URL: http://gw.knoxproxy.com:7000
Username: your_username
Password: your_passwordSet country targeting by modifying the username field.
Username: your_username-country-gbIn your extractor settings, select KnoxProxy as the proxy source under the "Advanced" tab.
For programmatic control, pass proxy settings in your API extraction requests.
curl -X POST "https://data.import.io/extractor/{id}/start" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"proxy": {"url": "http://your_username-country-us:your_password@gw.knoxproxy.com:7000"}}'Run a test extraction and check the results for correct geo-targeting and data integrity.
import requests
# Import.io API with KnoxProxy as external proxy
IMPORTIO_API_KEY = "your_importio_api_key"
EXTRACTOR_ID = "your_extractor_id"
proxy_config = {
"url": "http://your_username-country-us:your_password@gw.knoxproxy.com:7000"
}
response = requests.post(
f"https://data.import.io/extractor/{EXTRACTOR_ID}/start",
headers={"Authorization": f"Bearer {IMPORTIO_API_KEY}"},
json={"proxy": proxy_config}
)
print(f"Extraction started: {response.json()}")KnoxProxy automatically rotates IPs per request. For extractors that crawl paginated content, use sticky sessions to maintain consistent IP across pages.
| Problem | Fix |
|---|---|
| Extractor fails with proxy error | Verify the proxy URL format: http://user:pass@gw.knoxproxy.com:7000. Check that your Import.io plan supports external proxies. |
| Data returns from wrong region | Ensure username includes -country-{cc} suffix. Verify with a test extraction on an IP-checking site. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
KnoxProxy offers lower per-GB pricing than Import.io's built-in proxies, more granular country targeting across 195+ locations, and residential IPs with higher success rates on heavily protected sites. It also works both in the dashboard's Proxy Configuration screen and via the API for programmatic extractor requests, giving you one proxy layer for GUI and code-based workflows.
Yes. Once you add KnoxProxy under Settings > Proxy Configuration as an external proxy, every scheduled extraction inherits that setting automatically, with no per-run changes needed. KnoxProxy rotates IPs per request by default, or you can use sticky sessions to keep one IP across a paginated extractor's scheduled run.
Yes. Each extractor has its own Advanced tab proxy source setting, so set a different -country-{cc} suffix on the username per extractor, for example your_username-country-gb for UK data. This lets you run multiple extractors in parallel, each pulling geo-targeted results from a different KnoxProxy residential location at the same time.
KnoxProxy charges per GB of data transferred rather than per request or per extractor, unlike some Import.io built-in proxy options. Import.io extractions typically pull structured, lightweight page data rather than full media-heavy pages, so bandwidth use stays modest and costs remain low even when you run many scheduled extractions at scale.
Rotating residential proxies -- 5 minutes setup, instant activation, 14-day money-back guarantee.