Proxy mode

Plug requests, Scrapy, Selenium, Playwright or any HTTP client into WyndPath without changing your code: just point your proxy at WyndPath. Every request goes through the same pipeline as the REST API (anti-bot, sessions, billing, quota).

Format

http://<API_KEY>:<params>@proxy.wyndpath.com:8888
HTTPS. HTTPS targets are intercepted so the request can be read: disable TLS verification on the client side (verify=False / -k). WyndPath presents its own certificate.

curl

curl -x "http://wk_YOUR_KEY:render_js=1&[email protected]:8888" \
     -k "https://www.vinted.fr/api/v2/catalog/items?search_text=nike"

Python — requests

import requests

proxy = "http://wk_YOUR_KEY:[email protected]:8888"
r = requests.get(
    "https://www.vinted.fr/api/v2/catalog/items?search_text=nike",
    proxies={"http": proxy, "https": proxy},
    verify=False,
)
print(r.json()["items"][0]["title"])

Scrapy

# In a request's meta, or via a proxy middleware:
meta={"proxy": "http://wk_YOUR_KEY:[email protected]:8888"}
# Disable TLS verification: in settings, DOWNLOADER_CLIENT_TLS_METHOD stays
# at its default; use a client that tolerates the interception certificate.

Parameters

Every API parameter (see API parameters) is accepted in the password, separated by &: render_js, country, session, optimize_request, max_cost, retries… Encode special characters if needed.

Proxy mode or REST API?

Note. At the MVP stage, the proxy handles one request per connection (keep-alive is coming). Billing, credits and quota are identical to the REST API. Security (domain allowlist, anti-SSRF) applies the same way.