Get Active Orders
Account API
Get Active Orders
Retrieve all active orders with proxy details for a specific customer.
GET
Get Active Orders
Fetch all active orders for a specific customer, including full proxy lists.
Each proxy is separated by a newline character (
Request
Headers
| Header | Value | Required |
|---|---|---|
Authorization | Bearer {your_api_key} | Yes |
Path Parameters
The customer’s Discord ID or identifier.
Example Request
Response
Success Response
Response Fields
Array of active order objects with proxy details.
Order Object Fields
| Field | Type | Description |
|---|---|---|
_id | string | MongoDB document ID |
email | string | Customer’s email address |
customer_discord_id | string | Customer’s Discord ID |
product_id | string | Product type identifier |
product_name | string | Human-readable product name |
quantity | integer | Number of proxies |
order_status | string | Status (always “active” for this endpoint) |
unix_purchase_date | integer | Purchase timestamp |
unix_expiration_date | integer | Expiration timestamp |
datacenter_details | object | Proxy credentials and list |
Datacenter Details Object
| Field | Type | Description |
|---|---|---|
proxy_username | string | Authentication username |
proxy_password | string | Authentication password |
proxy_port | integer | Proxy port number |
proxy_list | string | Newline-separated list of proxies |
Error Responses
503 Service Unavailable
Proxy List Format
Theproxy_list field contains proxies in the format:
\n).
Example Parsing (JavaScript)
Difference from Order History
| Endpoint | Active Only | Includes Proxy List |
|---|---|---|
| Get Order History | No (all orders) | No |
| Get Active Orders | Yes | Yes |
Use Case
This endpoint is ideal for:- Retrieving ready-to-use proxy lists for a customer
- Automated proxy distribution systems
- Building customer-facing proxy management tools
