Reseller API

Agency and reseller access for offering ProxyOmega to your own customers at scale. The Reseller API lets you create and manage sub-accounts, provision subscriptions, and track usage programmatically, all under one approved reseller account.

i
This is a separate API. The Reseller API uses a different base URL and a different authentication scheme from the Public API. If you only need to manage your own account (whitelist, proxy-list export, usage stats), use the Public API instead.

Base URL

All Reseller API requests go to:

https://proxyomega.com/api/reseller/v1

Endpoint paths are appended to this base. The examples on this page use illustrative paths to show request shape. For the full, authoritative endpoint list, refer to the reseller documentation in your dashboard.

Authentication

The Reseller API authenticates with a bearer token. Send your reseller API key in the Authorization header on every request:

Authorization: Bearer <api_key>

Your reseller API key is issued in the dashboard once your reseller account is approved. Keep it secret and treat it like a password. Do not embed it in client-side code or commit it to version control.

i
Different from the Public API. The Public API is authenticated with the X-API-Key header at https://proxyomega.com/api. The Reseller API is authenticated with Authorization: Bearer <api_key> at https://proxyomega.com/api/reseller/v1. The two keys and base URLs are not interchangeable.

Example authenticated request

A minimal authenticated call using curl. Swap in your own key and endpoint:

curl https://proxyomega.com/api/reseller/v1/sub-accounts \
  -H "Authorization: Bearer <api_key>" \
  -H "Accept: application/json"

To create a resource, send a JSON body with the appropriate method:

curl -X POST https://proxyomega.com/api/reseller/v1/sub-accounts \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "label": "Client A"
  }'

Requirements

  • An approved reseller account. Reseller access is granted after you apply and are approved.
  • KYC verification. Your reseller account must complete identity verification before the API is enabled.
  • Sufficient account balance. There is no fixed minimum. Your balance only needs to cover each provisioning purchase at the moment you make it. Top up your balance in the dashboard before provisioning.

Capabilities

The Reseller API covers the full lifecycle of managing proxy access on behalf of your own customers:

Sub-account management

Create, update, and manage sub-accounts for each of your clients under your reseller umbrella.

Subscription provisioning

Provision proxy subscriptions across the product range directly against your account balance.

Analytics

Pull usage and performance analytics across your sub-accounts to report and reconcile.

Whitelist management

Manage IP whitelists per sub-account for credential-free proxy access.

Bandwidth tracking

Track bandwidth consumption for pay-as-you-go products and monitor usage against plans.

Port-config rotation

Manage per-port configuration and rotation for port-based subscriptions.

CapabilityWhat it does
Sub-account managementCreate and administer client sub-accounts under your reseller account.
Subscription provisioningBuy and assign proxy subscriptions on behalf of your clients.
AnalyticsRetrieve usage and performance data across your sub-accounts.
Whitelist managementAdd and remove authorised IPs for credential-free connections.
Bandwidth trackingMonitor GB consumption on pay-as-you-go products.
Port-config rotationConfigure and rotate per-port settings on port-based plans.

How to become a reseller

i
Apply and verify in the dashboard. Sign in at dashboard.proxyomega.com, apply for a reseller account, and complete KYC verification. Once approved and verified, your reseller API key is issued and the Reseller API is enabled. Questions about reseller access? Email [email protected].
  • Public API. Self-service API for managing your own account (X-API-Key auth).
  • Authentication. The three ways to authenticate proxy connections.
  • Targeting. Country, state, city, ASN, session, and TTL parameters.

Last updated July 6, 2026