Logo

Reseller FAQ and Common Scenarios

This guide addresses common questions and scenarios that resellers encounter. We've created detailed explanations with examples to help developers at any skill level understand our proxy system.

Frequently Asked Questions

"How do I generate a proxy?"

This is the most common question, and it shows a misunderstanding of how our system works.

The Answer: You don't "generate" proxies through an API - proxies are just credentials combined with our fixed endpoints.

A proxy string is formed by combining these components:

  1. Username (from your subuser account)
  2. Password (from your subuser account)
  3. Endpoint (our fixed domain for that proxy type)
  4. Port (our fixed port for that protocol)

The result is a standard proxy string in this format:

username:password@endpoint:port

Example:

customer123:[email protected]:1000

"Where is your API to create a new proxy?"

The Answer: There is no special API to "create" proxies. Instead:

  1. Use the reseller API to create a subuser account
  2. Add balance to that subuser
  3. The proxy is automatically available at our fixed endpoints

The proxy string is just:

[subuser_username]:[subuser_password]@[product_endpoint]:[product_port]

"How do I check how much data a user has used?"

The Answer: Use the usage history endpoint:

GET /v2/reseller/subusers/{username}/usage

This will return detailed usage information for the specified user.

"Can I use my own domain for proxies?"

The Answer: Yes! Set up a CNAME record on your domain:

  1. Create a subdomain (e.g., proxies.yourdomain.com)
  2. Point it to our server (e.g., rp.evomi.com)
  3. Your customers can then use: 
    username:[email protected]:1000

Common Scenarios with Solutions

Scenario 1: Setting Up a Reseller Dashboard

Problem: "I want to create a dashboard where customers can buy proxies and see their usage."

Solution:

  1. Set up user authentication for your dashboard
  2. When a user registers:
    • Create a subuser in our system with the reseller API
    • Store their credentials in your database
  3. Display proxy information constructed from their credentials
  4. Show balance and usage from the usage API
  5. Allow them to purchase more balance (through your payment processor)

Process Flow:

Registration:

  1. Customer registers on your dashboard
  2. Your backend creates a customer record
  3. Your backend calls Evomi API to create a subuser
  4. Evomi API confirms subuser creation
  5. Your backend tells the dashboard the account is ready
  6. Dashboard confirms registration to the customer

Purchase:

  1. Customer purchases 5GB of proxy data
  2. Your dashboard sends request to your backend
  3. Your backend processes payment
  4. Your backend calls Evomi API to add balance
  5. Evomi API confirms balance addition
  6. Your backend tells dashboard the balance is updated
  7. Dashboard notifies customer they're ready to use the service

View Proxies:

  1. Customer views proxy details in dashboard
  2. Dashboard asks your backend for customer info
  3. Your backend returns credentials
  4. Dashboard constructs proxy strings
  5. Dashboard displays proxy information to customer

Scenario 2: Customer Wants to Target Specific Countries

Problem: "My customer wants proxies from certain countries only."

Solution:

  1. The customer doesn't need "special proxies" for specific countries
  2. They use the SAME proxy credentials but modify the password:
// Basic proxy - worldwide IPs
const basicProxy = `${username}:${password}@rp.evomi.com:1000`;

// US proxy - just modify the password
const usProxy = `${username}:${password}[email protected]:1000`;

// UK proxy - just modify the password
const ukProxy = `${username}:${password}[email protected]:1000`;

Your dashboard can provide a UI where customers select countries and see the resulting proxy string.

Scenario 3: Tracking Usage and Billing

Problem: "How do I know when a customer runs out of data?"

Solution:

  1. The user sees his balance in the dashboard
  2. Once the user runs out, his proxy will stop working.

Request Flow Process

To further clarify how the system works, here's a step-by-step explanation of what happens when a customer uses a proxy:

1. Initial Connection:

  • Customer's client connects to our proxy server using username:password@endpoint:port
  • Our proxy server validates the credentials
  • Our proxy server checks available balance/quota
  • Our proxy server parses any password parameters

2. IP Selection Based on Parameters:

  • If _country-US is specified: Proxy selects a US IP address
  • If _session-xyz is specified: Proxy uses/maintains the same IP for that session
  • If no special parameters: Proxy selects a random IP

3. Request Handling:

  • Proxy forwards the request to the target website using the selected IP
  • Target website returns response to our proxy
  • Our proxy logs the bandwidth usage
  • Our proxy returns the response to the customer's client

This process happens for every request that goes through our proxy system, ensuring proper routing, authentication, and tracking.

Integration Checklist

Use this checklist to ensure your reseller platform is properly integrated:

  • Set up user authentication system
  • Integrate API key securely in backend
  • Create subuser accounts via API
  • Store credentials securely
  • Create UI to display proxy information
  • Set up payment processing
  • Integrate balance addition API
  • Create usage monitoring system
  • Set up automated alerts for low balance
  • Add country/session parameter UI (optional)
  • Configure custom domain CNAME records (optional)

Summary

Remember these key points:

  1. No "proxy generation" API - proxies are constructed from credentials + fixed endpoints
  2. Our system uses a balance model (data, time, or threads depending on product)
  3. All targeting and configuration happens via password parameters
  4. Custom domains can be set up via CNAME records
  5. Usage tracking is available via API

With these concepts clearly understood, even developers with limited experience should be able to successfully integrate and manage your reseller platform.