Direct customer
Connect applications to proxy gateways, generate credentials, and inspect your own traffic and sessions.
Make a proxy request →ProxyRequest platform documentation
ProxyRequest is the operating layer between proxy supply and the product your customers use. These guides cover both traffic connectivity and the control-plane workflows required to run a reseller platform.
Reseller platform
Provision sub-users, allocate bytes, generate proxy access, and keep your billing system synchronized.
Build the reseller flow →The platform surface
Section titled “The platform surface”01SupplyProviders and pools
02ProxyRequestProducts, users, limits
GatewaysHTTP and SOCKS5
Platform APIProvision and automate
AnalyticsReconcile usage
WebhooksReact to balance events
Proxy gateways
Route HTTP, HTTPS, SOCKS5, and SOCKS5h traffic with package credentials, geographic targeting, and sticky-session tokens.
Platform API
Manage users, orders, data allocation, proxy generation, analytics, API keys, and webhook destinations.
Accounting
Treat bytes as the shared unit across balances, child-order limits, analytics, and usage events.
Event delivery
Receive signed batches when user or order balances change, then reconcile them against analytics.
Resource model
Section titled “Resource model”The same identifiers appear in several API areas. Keep them in your own data model instead of inferring relationships from usernames.
| Resource | What it represents | Where it is reused |
|---|---|---|
| Main user | The authenticated customer or reseller account | Profile, packages, orders, analytics |
| Sub-user | A customer managed by a reseller | Data allocation, user orders, usage events |
| Package | A proxy product and its targeting capabilities | Orders, locations, generation |
| Order | Purchased or assigned access to a package | Credentials, balances, analytics |
| Ledger | The accounting balance used by traffic processing | Webhook events and reconciliation |
Integration principles
Section titled “Integration principles”- Keep secrets server-side. Proxy passwords, JWTs, API keys, and webhook secrets do not belong in browsers or public repositories.
- Store identifiers. Persist user, package, order, and ledger IDs alongside your own customer IDs.
- Send allocation values in bytes. Convert explicitly and avoid an ambiguous
GBlabel in business logic. - Cache catalogs, not balances. Package and location metadata change less frequently than usage state.
- Use webhooks for reaction and analytics for reconciliation. Event delivery reduces polling; analytics remains the reporting surface.
Recommended starting points
Section titled “Recommended starting points”Make the first proxy requestBuild safe credentials and test an HTTP or SOCKS5h connection.
Automate a reseller workflowCreate a sub-user, allocate bytes, and generate access.
Implement webhook deliveryVerify X-Signature and process the real accountant payload.
Browse the APISearch operations, schemas, responses, and generated snippets.