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.

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

Pick the client you already use. The pool, country and requested session stay in the Databay username.
14 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.

Browser automation

Configure the browser process or an isolated context before the first navigation.

3guides

Multi-profile browser

Keep the saved proxy route attached to the authorized profile that uses it.

6guides

Crawler framework

Put proxy selection and retry behavior at the crawler downloader boundary.

1guide

Command-line client

Inspect authentication, tunnel and destination behavior one hop at a time.

1guide

HTTP client library

Keep application requests, sessions and proxy-agent policy explicit.

3guides
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
# DATABAY_API_BASE comes from the linked API reference.
curl -X POST \
  "${DATABAY_API_BASE}/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.

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