Create a new proxy order. Orders are automatically billed through Stripe integration.
Request
| Header | Value | Required |
|---|
Authorization | Bearer {your_api_key} | Yes |
Content-Type | application/json | Yes |
Body Parameters
Number of proxies to order. Must be greater than 0.
Type of proxy product to order (e.g., "captcha", "x1", "level3").
Optional customer identifier for tracking. Must be lowercase letters only (a-z), max 50 characters.
Example Request
curl -X POST "https://dashboard.statproxies.com/api/v2/order/newscale" \
-H "Authorization: Bearer {your_api_key}" \
-H "Content-Type: application/json" \
-d '{
"quantity": 10,
"product_type": "captcha",
"customer": "clientabc"
}'
Response
Success Response
Status of the request. Returns "success" on successful order creation.
Unique identifier for the order. Use this to fetch proxy details.
Stripe subscription ID for billing management.
{
"response": "success",
"order_id": "sub_1rqjp3jb4g9i6pkhdwmkpjob",
"subscription_id": "sub_1RqJP3JB4G9i6PKHDwmKPJOb"
}
Error Responses
400 Bad Request - Missing Fields
{
"response": "Missing required fields"
}
400 Bad Request - Invalid Product Type
{
"response": "Invalid product_type"
}
400 Bad Request - Invalid Quantity
{
"response": "Quantity must be greater than 0"
}
400 Bad Request - Invalid Customer ID
{
"response": "Customer ID must contain only lowercase letters (a-z)"
}
401 Unauthorized
{
"error": "invalid_api_key"
}
Notes
- Orders are automatically billed through your connected Stripe account
- Proxy credentials become active immediately after successful order creation
- The
order_id is a lowercase version of the subscription ID and is used as the proxy username
- If using an organization API key, the order is billed to the organization’s Stripe customer