Proxy Generation for Resellers

This guide explains how to "generate" proxies for your customers without needing any special API endpoints.

Understanding Proxy Format

First, let's understand the format of every proxy:

username:password@endpoint:port

For example:

customer123:[email protected]:1000

There Is No "Generate Proxy" API!

One of the most common confusions for new resellers is expecting an API endpoint that "generates" or "creates" proxies.

Important: Our system does not use an API to create proxies. Instead, proxies are constructed by combining fixed endpoints with user credentials.

Why No Generation API?

Our approach is simpler and more flexible:

All proxy endpoints and ports are fixed per product type
You only need to create user accounts (with our reseller API)
Proxies are "generated" by combining user credentials with our endpoints

How to "Generate" Proxies for Your Customers

To provide a proxy to your customer:

Create a subuser account via the reseller API
Set their username and password
Add balance to their account
Construct the proxy string using the format:

[username]:[password]@[endpoint]:[port]

Example: Generating a Residential Proxy

// Step 1: You've already created a subuser with these credentials
const username = "customer123";
const password = "mySecretPass";

// Step 2: Choose the product (residential proxies in this case)
const endpoint = "rp.evomi.com";
const httpPort = 1000;
const socksPort = 1002;

// Step 3: "Generate" the HTTP proxy
const httpProxy = `${username}:${password}@${endpoint}:${httpPort}`;
// Result: customer123:[email protected]:1000

// Step 4: "Generate" the SOCKS proxy
const socksProxy = `${username}:${password}@${endpoint}:${socksPort}`;
// Result: customer123:[email protected]:1002

Proxy Types and Their Endpoints

Each proxy type has fixed endpoints and ports:

Proxy Products Overview:

Users can connect to three types of proxies: Residential, Datacenter, and Mobile
Each type has its own endpoint and associated ports for HTTP and SOCKS connections

Residential Proxies:

Endpoint: rp.evomi.com
HTTP Port: 1000
SOCKS Port: 1002

Datacenter Proxies:

Endpoint: dcp.evomi.com
HTTP Port: 2000
SOCKS Port: 2002

Mobile Proxies:

Endpoint: mp.evomi.com
HTTP Port: 3000
SOCKS Port: 3002

                          ┌─► rp.evomi.com ──┬─► HTTP: 1000
                          │                  └─► SOCKS: 1002
                          │
User ───► Chooses Type ───┼─► dcp.evomi.com ─┬─► HTTP: 2000
                          │                  └─► SOCKS: 2002
                          │
                          └─► mp.evomi.com ──┬─► HTTP: 3000
                                             └─► SOCKS: 3002

Residential Proxies

Endpoint: rp.evomi.com
HTTP Port: 1000
SOCKS5 Port: 1002

Datacenter Proxies

Endpoint: dcp.evomi.com
HTTP Port: 2000
SOCKS5 Port: 2002

Mobile Proxies

Endpoint: mp.evomi.com
HTTP Port: 3000
SOCKS5 Port: 3002

Advanced: Custom Proxy Parameters

The real power comes from modifying the proxy password with parameters. This allows customers to control country selection, sticky sessions, and more.

Password Parameter Format

originalPassword_parameter-value

Common Parameters

Parameter	Example	Description
country	_country-US	Routes through US IPs
session	_session-abcdefgh	Uses sticky IP (8-char string)
lifetime	_lifetime-60	Session lasts 60 minutes
city	_city-new.york	Routes through New York City
region	_region-western.cape	Routes through Western Cape region
isp	_isp-att	Routes through AT&T ISP

Multiple Parameters

You can combine multiple parameters:

password_country-US_session-abcdefgh_lifetime-60

Which means:

Route through US IPs
Maintain the same IP (using session ID "abcdefgh")
Keep this session for 60 minutes

Next Steps

Now that you understand how to generate proxies, the next section will explain how to integrate this into your reseller dashboard system.