Build your own customer experience around proxy-user provisioning, bandwidth allocation, usage records, and source-IP whitelists. Databay reseller access is qualified by sales; your business keeps ownership of checkout, billing, tax, support, and end-user controls.
Approval is not automatic; commercial terms and KYC requirements depend on the proposed account.
API-based account controls
Infrastructure operations, not a hosted storefront.
Contact-sales onboarding
Commercial scope is reviewed before access.
KYC may apply
Verification depends on the proposed account.
Reseller owns end-user operations
Read the reseller termsReselling proxy access, proposing an ecosystem listing, and buying higher volume are not interchangeable. Databay publishes one owner for each request so a directory listing is not mistaken for reseller terms and a volume inquiry is not mistaken for permission to serve end users.
Resale
Apply for an approved account workflow that can create proxy users, allocate bandwidth, read usage, and manage source-IP whitelists. Your business owns the storefront, billing, tax, support, customer terms, and abuse controls.
Boundary: No margin, reseller rate, white-label feature, approval window, or service level is promised before written qualification.
Referral or ecosystem listing
Use the Partners directory to propose a product for compatibility review, integration testing, and a possible listing. That directory, not this reseller page, owns the ecosystem and integration path.
Boundary: Databay does not publish an affiliate commission, referral payout, revenue share, or guaranteed listing. A directory listing does not grant resale access.
Volume or custom requirements
If your team remains the end user but needs a higher-volume purchase, 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.
Boundary: Public product pages remain the source for standard capabilities and prices. No volume discount, custom availability, or custom SLA is implied by making contact.
The API is a bounded infrastructure layer. These route templates show the current operation families without inventing a hosted billing system, customer portal, or automatic commercial approval.
Inspect the API ↗Provision
Start with one proxy-user record that your own customer model can reference.
Provision a proxy user
Create credentials for an approved customer allocation.
/api/v{version}/accounts/{accountId}/proxy-usersAllocate
Transfer approved traffic, then read the records needed by your metering workflow.
Allocate bandwidth
Transfer an approved product allowance and expiration to that user.
/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/bandwidthsRead usage logs
Retrieve proxy-user traffic records for your own metering workflow.
/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/bandwidths/logsAuthorize
Read, add, and remove source-IP records through the approved account scope.
List source IPs
Read the source-IP whitelist records assigned to a proxy user.
/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/whitelisted-ipsManage source IPs
Add a permitted source-IP whitelist record to a proxy user.
/api/v{version}/accounts/{accountId}/proxy-users/{proxyUserId}/whitelisted-ipsRemove a source IP
Delete a permitted source-IP whitelist record by its identifier.
/api/v{version}/accounts/{accountId}/whitelist/{whitelistedIpId}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.
It fits a business that already owns its customer and commercial systems and needs programmable proxy infrastructure behind them. The review rows separate API-backed capabilities from decisions your team must make before sales can qualify the account.
Databay scope
Approved reseller accounts can create, list, update, and delete proxy users through the account API.
Your qualification check
Define how your system maps one customer to one proxy user and protects credentials.
Databay scope
The API can read a proxy user’s traffic allocation and transfer bandwidth with a product and expiration.
Your qualification check
Model failed transfers, expiration, balance checks, and idempotent retries before launch.
Databay scope
The API exposes traffic details and bandwidth logs for a specified proxy user.
Your qualification check
Decide how often to reconcile usage and how your customer-facing meter handles delay or disagreement.
Databay scope
Proxy-user whitelist records can be listed and added; account APIs also support removing whitelist entries.
Your qualification check
Build validation, ownership checks, audit history, and a safe removal path into your application.
Databay scope
Pricing, account approval, product scope, limits, and onboarding are handled through sales.
Your qualification check
Bring a volume forecast, target markets, required networks, concurrency, and launch timeline.
The API handles infrastructure operations. It does not replace the commercial and compliance gates around those operations.
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.
Keep your customer record, plan, payment state, tax treatment, and support history in your own system. Store the Databay proxy-user identifier as an infrastructure reference.
Create the proxy user, transfer the approved bandwidth, and configure source-IP whitelists only after your onboarding and payment rules pass.
Read traffic details and logs on a documented schedule. Preserve allocation, transfer, usage, and whitelist events so support and disputes can be investigated.
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.
A serious reseller plan makes ownership explicit before integration. These columns are intentionally asymmetric: Databay supplies a bounded infrastructure layer, while the reseller owns the customer business built on top of it.
Databay scope
Reseller scope
The commercial-reselling section 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.
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.
Sources checked : the public account API and four-product catalogue, plus Terms, KYC Policy, and Acceptable Use Policy updated July 25, 2026. Approval is not automatic; commercial terms and KYC requirements depend on the proposed account.
Scope, pricing, white-label requirements, KYC, billing, and support all need explicit ownership before launch.
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.
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.
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.
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.
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.
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.
Send sales the products, markets, traffic forecast, customer model, required controls, and launch timeline. The reply can then address scope, review, and commercial terms.
Include in the first message
Contact-sales pricing. KYC may apply. No instant approval, margin, discount, custom SLA, or unconfirmed white-label feature is promised.