Gateway integration
Send traffic through a deployed ProxyRequest gateway, verify credentials, and add targeting or sessions.
Open the gateway quickstart →ProxyRequest platform documentation
ProxyRequest supplies a managed proxy backend and a complete customer dashboard for resellers and operators. Use them together, or keep your existing frontend and billing while ProxyRequest runs routing, provisioning, accounting, and analytics headlessly.
Integrate your system
Section titled “Integrate your system”Choose the workflow that matches how you fund customer access. Start with one complete purchase or allocation, then verify a real proxy request and its usage.
Use your own billingCreate a customer, record a verified paid purchase, and deliver independently funded proxy access.
Build a reseller integrationFund a parent package, assign customer quotas, and monitor the shared pool.
Not sure which model you need? Read how purchases, quotas and ledgers fit together. For another task, use the complete API workflow map.
White-label platform
Connect supply, create a package and customer, generate access, and validate accounting end to end.
Launch a test product →Customer dashboard
Review the supplied customer and reseller frontend, brand setup, security controls, and launch inputs.
Review the dashboard →Headless integration
Keep your own users, products, billing, and UI while mapping access to ProxyRequest provisioning and analytics.
Build a headless integration →The platform surface
Section titled “The platform surface”01SupplyProviders and pools
02ProxyRequestProducts, users, limits
Customer dashboardBuy, manage, and resell
GatewaysHTTP and SOCKS5
Platform APIProvision and automate
AnalyticsReconcile usage
WebhooksReact to balance events
Proxy gateways
Route HTTP, HTTPS, SOCKS5, and SOCKS5h traffic through compatible upstream providers with geographic targeting, sticky sessions, provider mixing, and one branded endpoint.
Platform API
Manage users, packages, orders, data allocation, proxy generation, analytics, API keys, and webhook destinations.
Customer dashboard
Give customers and resellers sign-in, packages, purchasing, credentials, usage, invoices, account security, and managed-user workflows connected to the same backend resources.
Customer control and accounting
Enforce credentials, traffic allowances, connection limits, IP allowlists, and domain blocklists using bytes as the shared accounting unit.
Commercial workflows
Use the built-in purchase and invoice flow or keep billing in your own control plane and provision access through the REST API.
Operational evidence
Inspect usage, requests, connections, errors, provider health, alerts, and incident history through operator-facing surfaces.
Event delivery
Receive signed batches when user or order balances change, then reconcile them against analytics.
Choose how to run the platform
Section titled “Choose how to run the platform”Complete white-label platform
Use the supplied dashboard, users, packages, orders, purchase flow, accounting, analytics, and gateway infrastructure as one product. Every plan includes the dashboard and base brand styling; separately quoted customization is available with six- or twelve-month prepayment.
Headless infrastructure
Keep your existing frontend, customer model, and billing. Map those records to ProxyRequest resources and use the API for provisioning and reporting.
Operating boundary
Section titled “Operating boundary”ProxyRequest SaaS is the product and control layer between upstream proxy supply and the customers who consume it. The operator keeps control of upstream provider contracts. ProxyRequest provides and operates the standard gateway server footprint.
| Responsibility | Operator | ProxyRequest SaaS |
|---|---|---|
| Brand, marketing site, pricing, legal terms, and customer support | Owns | Supplies the customer dashboard and APIs |
| Dashboard identity and configuration | Supplies final assets, domains, links, copy, and approvals | Applies base brand styling on every plan; offers separately quoted customization on six-/twelve-month prepaid terms |
| Upstream providers and their commercial contracts | Owns | Connects and routes configured supply |
| Proxy gateway servers | Chooses deployment regions, expected load, and package gateway scope | Provides and fully manages two VPS instances by default, including provisioning, hardening, DNS and ports, updates, monitoring, and replacement |
| Users, packages, orders, credentials, and usage policy | Chooses the commercial model | Enforces the mirrored platform resources |
| Managed control and data services | Consumes through the UI and API | Operates the services, storage, accounting, and automation |
Every plan includes two fully managed gateway VPS instances for new subscriptions and renewals. Each VPS has a network port up to 1 Gbps and can be placed in any combination of EU, US, or Asia, including both servers in one region. Additional servers or higher capacity are scoped separately. Customer-provided container hosts or Kubernetes remain available as an advanced deployment option.
Core behavior and boundaries
Section titled “Core behavior and boundaries”Supply, targeting, and protocols
Products can mix compatible upstreams behind one endpoint. Available geography, network targeting, protocols, and session behavior depend on the package and eligible provider inventory.
Routing and failures
Weights apply only after incompatible or unhealthy routes are excluded. The gateway does not silently broaden geography or replay failed application requests.
Customers and accounting
Users, orders, and ledgers connect access policy to integer-byte accounting. Usage is batched, so a final record can cross the exact byte boundary.
Analytics and reconciliation
The dashboard and API expose customer usage and request evidence. Signed webhooks support prompt updates; closed analytics windows remain the reconciliation surface.
Recommended starting points
Section titled “Recommended starting points”Review the customer dashboardSee included workflows, screenshots, base brand styling, security controls, and launch requirements.
Launch a test proxy productConnect supply, verify the managed gateways, create a customer, and validate usage end to end.
Test gateway connectivityUse issued credentials to test an HTTP or SOCKS5h connection.
Automate a reseller workflowCreate a sub-user, allocate bytes, and generate access.
Keep your own control planeMap existing users and products into a hybrid headless integration.
Migrate an existing proxy businessMove products, balances, credentials, and customers in controlled batches with a tested rollback path.
Implement webhook deliveryVerify X-Signature and process the real accountant payload.
Browse the APISearch operations, schemas, responses, and generated snippets.