Integrations

Route your tool
through one gateway.

Every guide points a different runtime at the same endpoint, gw.databay.co:8888. Pick the tool you use and copy a setup that keeps country, session and browser identity aligned.

Start freeBrowse the guides

HTTP proxying, HTTPS CONNECT, and SOCKS5. No SDK to install.

ONE GATEWAYgw.databay.co:8888ResidentialISP originDatacenterhosting origin
11 Maintained guides
3 Documented proxy modes
195 Published paid-location routes
120 min Max sticky session
One endpoint: gw.databay.co:8888HTTP proxying, HTTPS CONNECT, and SOCKS5No SDK or client libraryGeo-targeting at no extra costAutomate with the API
Setup guides

Choose the guide that matches your runtime

Each runtime attaches proxy settings in a different place. Every guide below maps the tool's native controls to the same gateway, then keeps pool, country and session aligned.

  • Multi-profile browser

    GoLogin

    Current Location-column setup, Proxy Manager imports, HTTP or SOCKS5 credentials, connection checks, bulk assignment, and API updates.

    Location column -> external proxy -> connection check -> assigned profile

    Updated · 14 min
  • Multi-profile browser

    Dolphin Anty

    Documented HTTP or SOCKS5 formats, the Proxy screen checker, per-profile assignment, bulk controls, and same-account sharing.

    Proxy screen -> connection check -> saved route -> assigned profile

    Updated · 13 min
  • Multi-profile browser

    AdsPower

    Per-profile HTTP or SOCKS5 setup, the saved Proxies list, bulk profile imports, and Local API provisioning.

    Proxies list -> per-profile flags -> pinned exits

    Updated · 12 min
  • HTTP client library

    Axios

    Axios 1.18 HTTP and HTTPS routing, environment precedence, agent boundaries, credential redaction, 407 attribution and bounded timeouts.

    Axios request -> route selector -> absolute-form or CONNECT -> hop evidence

    Updated · 18 min
  • Command-line client

    cURL

    HTTP proxying, HTTPS CONNECT, and SOCKS5 with proxy-side DNS setup, credential handling, 407 diagnosis, timeouts and machine-readable evidence.

    curl -> proxy auth -> CONNECT or SOCKS -> approved destination

    Updated · 16 min
  • HTTP client library

    Node.js fetch

    Node 24 built-in environment support, runtime global policy, per-request ProxyAgent, version compatibility, 407 and timeout diagnosis.

    fetch -> env opt-in or same-package dispatcher -> proxy evidence

    Updated · 13 min
  • HTTP client library

    Python Requests

    HTTP and SOCKS setup, environment precedence, Session pooling, bounded retries, timeout semantics and exception diagnosis.

    Session -> HTTPAdapter policy -> proxy hop -> approved destination

    Updated · 18 min
  • Browser automation

    Playwright

    Launch-level and per-context proxies across Chromium, Firefox and WebKit, with rotation patterns.

    Browser process -> isolated contexts -> independent exit sessions

    Updated · 9 min
  • Browser automation

    Puppeteer

    Chromium launch flags, page authentication, sticky rotation and production failure handling.

    --proxy-server -> page.authenticate() -> page.goto()

    Updated · 9 min
  • Crawler framework

    Scrapy

    Request metadata, project-wide middleware, domain sessions and throughput-aware retries.

    Request queue -> downloader middleware -> rotating exit pool

    Updated · 10 min
  • Browser automation

    Selenium

    Chrome and Firefox setup, IP whitelisting, Selenium Wire and a Chrome extension fallback.

    WebDriver -> auth decision -> Databay gateway

    Updated · 10 min
Shared contract

The tool changes. The gateway grammar does not.

Every guide resolves to the same three decisions: where traffic enters, which pool and geography it should use, and whether the exit must stay attached to an identity.

  • One endpoint for HTTP proxying, HTTPS CONNECT, and SOCKS5
  • Pool and geography selected in the username
  • Requested sticky window up to 120 minutes; continuity can end early
  • Country targeting on supported products, with no targeting surcharge
Browse proxy locations
01 / Gatewaygw.databay.co:8888

One host and port for HTTP proxying, HTTPS CONNECT, and SOCKS5.

02 / Routing policyUSER-zone-{pool}-countryCode-{cc}-sessionId-{identity}

Pool, geography and persistence live in the username.

03 / Verificationcurl --proxy http://gw.databay.co:8888 https://httpbin.org/ip

Check the exit from the same runtime that will run the job.

Control plane

Automate the setup around the runtime

Use the REST API to provision proxy users, manage IP whitelists, read bandwidth and query locations. Your browser or crawler still connects over the same gateway.

  • Create, update and delete proxy users
  • Monitor bandwidth usage and traffic logs
  • Manage IP whitelists for static workers
  • Request one country, city, or ASN constraint at a time on Premium Residential
Read the API reference(opens in a new tab)
Authenticated requestPOST /proxy-users
curl -X POST \
  https://api.databay.com/api/v1/accounts/{accountId}/proxy-users \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "username": "scraper_us",
    "password": "securePass123"
  }'
Setup FAQ

Gateway questions, answered

Which protocols do Databay proxies support?
HTTP proxying, HTTPS CONNECT, and SOCKS5, all on the same gateway (gw.databay.co:8888). Configure an HTTP proxy for HTTP proxying and HTTPS CONNECT, or SOCKS5 where the client supports it; there are no separate endpoints or mode surcharges.
Do I need a special client or SDK?
No. Databay uses standard proxy protocols, so any software with proxy support (browsers, scrapers, automation frameworks, even OS-level network settings) connects without extra libraries. The guides above are configuration, not custom code.
How do sticky sessions work?
Without a named session, each new proxy connection may select an available exit; a different or fresh IP is not guaranteed. Premium Residential, Datacenter, and Mobile accept requested sticky windows up to 120 minutes, while Residential Flex accepts up to 30 minutes. Upstream availability can end continuity sooner.
Can I target specific countries?
Yes. On a supported product, append one country code to the proxy username (for example USER-zone-residential-countryCode-us). Route availability is product-specific, and observed geography should be verified.

Connect your tool in minutes

Create an account, grab your gateway credentials, and route your first request today. Using a tool that is not listed yet? Ask us and we will map the exact connection path.

Create accountRequest a guide

Works with clients that accept standard HTTP(S) or SOCKS5 proxy credentials.