Skip to main content
GET
Get Customer Orders
Retrieve all non-expired orders tagged with a specific customer ID, including proxy details. Proxies are always returned as ip:port:username:password strings.

Request

Headers

Path Parameters

string
required
The customer ID to search for. Letters a-z only. Uppercase letters are converted to lowercase.

Query Parameters

string
http (default) or socks5. With socks5, each proxy comes back with the SOCKS5 port in place of the HTTP port. The IPs, username and password stay the same. Leave it off and you get the same HTTP list as before. Any other value returns 400.
string
windows, macos, ios or linux. Adds -os-<value> to each username in proxies to choose that TCP/IP fingerprint. The password, IP and port stay the same. Leave it off for the default list. Any other value, including android, returns 400.

Example Requests

Response

Success Response

Response Fields

string
Status of the request.
string
The customer ID that was searched.
integer
Total number of orders found for this customer.
array
Array of order objects with proxy details.

Order Object Fields

Error Responses

400 Bad Request - Invalid Customer ID

400 Bad Request - Invalid Protocol

400 Bad Request - Invalid Fingerprint

404 Not Found - No Orders

Add ?fingerprint=windows|macos|ios|linux to get every proxy with a TCP/IP fingerprint suffix on the username. See TCP Fingerprint Profiles.

Use Case

The customer ID feature is useful for:
  • Resellers: Track orders for specific clients
  • Enterprises: Organize proxies by department or project
  • Automation: Programmatically manage proxies per customer
When creating orders via the API, you can specify a customer parameter to tag orders for later retrieval using this endpoint.

Example Workflow