Skip to content
1 GB of residential proxies, free. $0 today, card required.

Resell Databay proxies through our API.

Provision proxy users, allocate bandwidth, read usage and manage allowlists from your own system. You own the customer; we run the network. Apply with your use case and expected volume.

Sales reviews each application, and KYC may apply depending on the account. Pricing and product scope are confirmed in writing.

Who runs whatAfter approval

Yours

Your customers
They sign up, pay and get support from you.
Your platform
Checkout, invoicing, tax, support, end-user terms and abuse controls.

Ours

Databay network
Products as approved for your account.
  • Residential
  • Residential Eco
  • Mobile
  • Datacenter

Before you apply

Three requests, three different owners.

Reselling proxy access, listing a tool and buying more volume are not interchangeable. Each has its own owner, so a directory listing is never mistaken for reseller terms, or a volume order for permission to serve end users.

ResaleThis page

You sell access to your customers

Apply for an approved account workflow that creates proxy users, allocates bandwidth, reads usage and manages source-IP allowlists. Your business owns the storefront, billing, tax, support, customer terms and abuse controls.

No margin, reseller rate, white-label feature, approval window, or service level is promised before written qualification.

Qualify a resale model

Referral or listingPartners

You build a proxy-aware tool

Propose your product for compatibility review, integration testing and a possible listing. The Partners directory, not this reseller page, owns the ecosystem and integration path.

A directory listing is not a revenue share or a guaranteed listing and does not grant resale access. Referral commission is a separate program with published terms on the referral page.

Review the partner path

Volume buyingSales

You buy for your own operation

Your team stays the end user but needs a higher-volume purchase, an operating-limit review or a written procurement scope. Send sales the products, traffic forecast, concurrency, markets and launch timeline. That is a direct buying request, not resale.

Public product pages remain the source for standard capabilities and prices. No volume discount, custom availability, or custom SLA is implied by making contact.

Discuss volume requirementsSee enterprise plans

How it works

From approval to reconciliation.

The API handles infrastructure operations. It does not replace the commercial and compliance gates around those operations.

  1. With Databay sales

    Qualify the account

    Tell sales what you plan to resell, expected volume, markets, customer profile, technical architecture and support model.

    Approval is not automatic, and KYC may apply.

  2. In your system

    Map your customer model

    Keep the customer record, plan, payment state, tax treatment and support history in your own system. Store the Databay proxy-user identifier as an infrastructure reference.

  3. Your system calls the API

    Provision access by API

    Create the proxy user, transfer the approved bandwidth and configure source-IP whitelists only after your onboarding and payment rules pass.

  4. Your system calls the API

    Reconcile usage

    Read traffic details and logs on a documented schedule. Preserve allocation, transfer, usage and whitelist events so support and disputes can be investigated.

  5. In your operation

    Enforce the downstream rules

    Apply your customer limits and stop conditions, investigate misuse and suspend access when required. Databay’s Terms and Acceptable Use Policy still govern every end user.

No instant approval. Do not build a launch plan that assumes access, pricing, product limits, or a white-label feature before sales confirms the written scope.

Account API

Run every customer’s access from your own code.

The published v1 account API covers the proxy-user lifecycle for approved accounts. The route templates show the operation families without inventing a hosted billing system, customer portal, or automatic commercial approval.

Inspect the API(opens in a new tab)

Provision users

Create proxy credentials for each customer from your own system. Approved accounts can create, list, update and delete proxy users.

  • POSTProvision a proxy user/api/v{version}/accounts/{accountId}/proxy-users

Your buildDefine how your system maps one customer to one proxy user and protects credentials.

Allocate bandwidth

Move purchased traffic to a customer with a product and an expiry, and read that user’s traffic allocation.

  • POSTTransfer bandwidth/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/bandwidths

Your buildModel failed transfers, expiration, balance checks, and idempotent retries before launch.

Read usage

Pull traffic details and bandwidth logs per user for your own metering and billing.

  • GETRead usage logs/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/bandwidths/logs

Your buildDecide how often to reconcile usage and how your customer-facing meter handles delay or disagreement.

Manage allowlists

Control which source IPs may connect for each proxy user: list, add and remove whitelist records.

  • GETPOSTList and add source IPs/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/whitelisted-ips
  • DELETERemove a source IP/api/v{version}/accounts/{accountId}/whitelist/{whitelistedIpId}

Your buildBuild validation, ownership checks, audit history, and a safe removal path into your application.

Route templates mirror the published v1 account API; replace each placeholder with an authorized account value. The current API reference, permissions, validation rules, and rate limits control.

Responsibility split

You own the customer. We run the network.

A serious reseller plan makes ownership explicit before integration. The split is intentionally uneven: Databay supplies a bounded infrastructure layer, while the reseller owns the customer business built on top of it.

Your scope

Customer operations

  • Customer checkout, invoicing, payment collection, refunds, and tax handling
  • Customer identity and risk review, including any KYC controls your model requires
  • Your customer portal, product packaging, margins, and customer-facing service terms
  • First-line customer support, credential recovery, notices, and incident communication
  • End-user limits, abuse response, access suspension, and required contractual flow-downs

Databay scope

Proxy infrastructure

  • Approved account API access for proxy-user lifecycle operations
  • Bandwidth allocation and proxy-user traffic records exposed by the API
  • Proxy-user source-IP whitelist management
  • Residential, Residential Eco, datacenter, and mobile product access as approved
  • Sales qualification for commercial scope, pricing, limits, and onboarding

The commercial-reselling section (§10.7) of the Databay Terms of Use makes the reseller responsible for end-user activity and requires a written end-user agreement at least as restrictive as Databay’s Terms and Acceptable Use Policy. Review those obligations with qualified counsel for your business and jurisdictions.

Qualification

Bring these answers to the first message.

Sales handles pricing, account approval, product scope, limits and onboarding. A concrete brief makes it possible to assess product fit, account controls, compliance review and commercial scope without implying that every requested capability is available.

Your brief

Product and traffic shape

  1. Products and target countries your customers actually need
  2. Expected monthly traffic, order pattern, concurrency, and growth range

Integration and recovery

  1. Required API operations and your recovery behavior when an operation fails
  2. Your checkout, invoicing, tax, refund, and customer-support ownership

Terms and risk controls

  1. End-user agreement with Terms and AUP obligations flowed down
  2. KYC, fraud, sanctions, privacy, retention, and abuse-escalation controls

Launch ownership

  1. Launch owner, engineering contact, abuse contact, and support coverage
  2. Any white-label requirement to discuss with sales without assuming availability
Send the qualification brief

Opens an email to sales with these eight prompts, ready to answer.

Reference

Reseller program questions.

Scope, pricing, white-label requirements, KYC, billing and support all need explicit ownership before launch.

What is the Databay proxy reseller program?

It is a contact-sales arrangement for approved businesses that want to build a customer-facing proxy offer around Databay account APIs. The reseller operates its own commercial and end-user workflow; Databay supplies only the approved network and API scope agreed during onboarding.

What can an approved reseller automate through the API?

The published account API includes proxy-user creation and management, bandwidth allocation and traffic details, usage logs, and proxy-user whitelist operations. Confirm the current endpoints, limits, authentication, and product scope in the API reference and with sales before designing production behavior.

Is white-label proxy infrastructure included?

This page does not promise custom branding, branded endpoints, a hosted portal, or another white-label feature. If white-label presentation is a requirement, list the exact capability and ask sales whether it can be included in your proposed arrangement.

How is proxy reseller pricing calculated?

Pricing is not published as a universal reseller rate. Sales qualifies the products, expected traffic, operating limits, customer model, and support needs before proposing commercial terms. No margin or resale price is guaranteed.

Does a proxy reseller account require KYC?

It may. Databay’s KYC Policy identifies higher-volume purchasing, higher operational limits, and specific enterprise or reseller agreements as potential verification triggers. Sales and compliance confirm the required review for the proposed account.

Who bills and supports the reseller’s end customers?

The reseller does. Your business owns checkout, invoicing, tax treatment, refunds, first-line support, customer notices, and end-user controls. Databay has no direct contractual relationship with your end users under the commercial-reselling section of its Terms.

Apply

Tell us what you plan to resell.

Send sales the products, markets, traffic forecast, customer model, required controls, and launch timeline. The reply can then address scope, review, and commercial terms.

Opens your email app, addressed to sales@databay.com.

Contact-sales pricing. KYC may apply. No instant approval, margin, discount, custom SLA, or unconfirmed white-label feature is promised.