API documentation
API URL
https://autoreg.site/api/
Endpoint: https://autoreg.site/api/get_balance
To check your balance (Token obtained from user history/Api key page), make the following API call.
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
Response | |||||
---|---|---|---|---|---|
api_token | string | Api token | balance | string | Balance value |
currency | string | Currency |
Examples:
CURL
1curl --location 'https://autoreg.site/api/get_balance?api_token=YOUR_API_TOKEN'
Response
1{
2 "api_token": "YOUR_API_TOKEN",
3 "balance": 25.68222
4 "currency": "USD"
5}
Endpoint: https://autoreg.site/api/product_list
List of all products on the website, their availability, and a unique identifier 'uni' through which you should make a purchase in the next request. uni is an array of keys.
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
Response | |||||
---|---|---|---|---|---|
product_name | string | Product name | price | number | The price per unit |
currency | string | Currency | count | integer | Availability |
uni | array | Uni - an array of unique product identifiers, to be used in the next request for purchase (use as an array). |
Examples:
CURL
1curl --location 'https://autoreg.site/api/product_list?api_token=YOUR_API_TOKEN'
Response
1{
2 "D-ID": [
3 {
4 "product_name": "D-ID (video)⚡️ on balance 5$",
5 "price": "0.05",
6 "currency": "USD",
7 "count": 13326,
8 "uni": [
9 "9e9881814f4ab7fca348de8d62155826"
10 ]
11 }
12 ],
13 "deepgram": [
14 {
15 "product_name": "deepgram.com - email - (audio)⚡️Credit 200$",
16 "price": "0.03",
17 "currency": "USD",
18 "count": 13207,
19 "uni": [
20 "46675fcb5456cb909492ab7bae025e30",
21 "d68abf293818719b2b69e252d19349bd"
22 ]
23 }
24 ],
25 "Discord": [
26 {
27 "product_name": "Discord - gmail.com | token",
28 "price": "0.01",
29 "currency": "USD",
30 "count": 0,
31 "uni": [
32 "1bfd6f67b5374230ee440a93ed94ff2f"
33 ]
34 },
35 {
36 "product_name": "Discord - phone | token",
37 "price": "0.035",
38 "currency": "USD",
39 "count": 15,
40 "uni": [
41 "102799df07be6b50eaaf9ab12abf07c4"
42 ]
43 }
44}
Endpoint: https://autoreg.site/api/new_order
Purchasing accounts - you specify the uni array obtained from the previous request, along with the quantity (count). If the required amount is available in the balance, the purchase will be completed. If the specified quantity is not available, all available accounts will be purchased.
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
uni | array | Required | Unique product identifier array (from product_list) |
count | integer | Required | Number of accounts to purchase |
Response | |||||
---|---|---|---|---|---|
status | integer | Response status code | message | string | Response status message |
order_key | string | Unique order identifier for downloading |
Examples:
CURL
1curl --location 'https://autoreg.site/api/new_order' \
2--header 'Content-Type: application/json' \
3--data '{
4 "api_token": "YOUR_API_TOKEN",
5 "uni": [
6 "68b3e2d954e66c764c1dfc7ef94128c6"
7 ],
8 "count": 10
9 }'
Response error
1{
2 "status": 400,
3 "message": "Negative balance"
4}
Response success
1{
2 "status": 200,
3 "message": "Success",
4 "order_key": "114daa5c50236970a78a623aaae7480c"
5}
Endpoint: https://autoreg.site/api/download
Check order status and download purchased items. Using the order_key obtained from the previous request, you can check if your order is ready and get the download link when processing is complete.
Order Processing Flow:
- Initial Status: When order is first created, status will be 200 with message "Waiting"
- Processing: Order is being prepared (continue checking status)
- Ready: When processing is complete, you'll receive a download URL
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
order_key | string | Required | Order_key from previous request |
Response | |||||
---|---|---|---|---|---|
status | integer | Response status code (200 for both waiting and ready states) | message | string | "Waiting" (processing) or "Success" (ready for download) |
data | object | Contains download_url when order is ready | download_url | string | Direct link to download your accounts (only when ready) |
Examples:
CURL
1curl --location 'https://autoreg.site/api/download?api_token=YOUR_API_TOKEN&order_key=YOUR_ORDER_KEY'
Response - Order Processing (Waiting)
1{
2 "status": 200,
3 "message": "Waiting"
4}
Response - Order Ready (Success)
1{
2 "status": 200,
3 "message": "Success",
4 "data": {
5 "download_url": "https://autoreg.site/status/cd45ea260db41233e98ae377daf93efc?download=1"
6 }
7}
Usage Example (Polling)
1# Keep checking order status until ready
2while true; do
3 response=$(curl -s "https://autoreg.site/api/download?api_token=YOUR_API_TOKEN&order_key=YOUR_ORDER_KEY")
4 message=$(echo $response | jq -r '.message')
5
6 if [ "$message" = "Success" ]; then
7 download_url=$(echo $response | jq -r '.data.download_url')
8 echo "Order ready! Download URL: $download_url"
9 break
10 elif [ "$message" = "Waiting" ]; then
11 echo "Order still processing, waiting..."
12 sleep 10
13 else
14 echo "Error: $response"
15 break
16 fi
17done
Important Notes:
- Polling Recommended: Check order status every 10-30 seconds until message changes from "Waiting" to "Success"
- Download URL: The download URL is direct and ready to use - you can download the file immediately
- File Format: Downloaded files may be in different formats depending on the product type (TXT, ZIP, etc.)
- Processing Time: Order processing time varies depending on product type and quantity
Endpoint: https://autoreg.site/api/order_list
Retrieve a list of your orders with filtering and pagination options. You can filter by status, payment status, payment type, URL, and creation date.
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
url | string | Optional | Filter by URL (partial match) |
status | string | Optional | Filter by order status (complete, waiting, success) |
payment_status | string | Optional | Filter by payment status (complete, waiting, success) |
created_at | string | Optional | Filter by specific date (YYYY-MM-DD) |
created_at_from | string | Optional | Filter from date (YYYY-MM-DD) |
created_at_to | string | Optional | Filter to date (YYYY-MM-DD) |
limit | integer | Optional | Number of records to return (default: 100, max: 1000) |
offset | integer | Optional | Number of records to skip (default: 0) |
Response | |||||
---|---|---|---|---|---|
orders | array | Array of order objects with the following fields: | |||
url | string | Product URL | product_type | string | Type of product |
product_name | string | Product name | status | string | Order status |
payment_status | string | Payment status | count | integer | Number of items |
price | number | Price per unit | sum | number | Total amount |
payment_type | string | Payment method | payment_amount | number | Payment amount |
payment_c_date | string | Payment completion date | discount | number | Applied discount |
product_description | string | Product description | user_email | string | User email |
created_at | string | Order creation date | pagination | object | Pagination information |
Examples:
CURL - Get all orders
1curl --location 'https://autoreg.site/api/order_list?api_token=YOUR_API_TOKEN'
CURL - Get orders with filters
1curl --location 'https://autoreg.site/api/order_list?api_token=YOUR_API_TOKEN&status=completed&payment_status=complete&limit=50&offset=0'
CURL - Get orders by date range
1curl --location 'https://autoreg.site/api/order_list?api_token=YOUR_API_TOKEN&created_at_from=2024-01-01&created_at_to=2024-12-31'
Response
1{
2 "orders": [
3 {
4 "url": "31234455665be28b3989875fcc1a",
5 "product_type": "Discord",
6 "product_name": "Discord - gmail.com | token",
7 "status": "completed",
8 "payment_status": "complete",
9 "count": 5,
10 "price": "0.01",
11 "sum": "0.05",
12 "payment_type": "trx",
13 "payment_amount": "0.05",
14 "payment_c_date": "2024-06-23 10:30:00",
15 "discount": "0.00",
16 "product_description": "Discord accounts with gmail verification",
17 "user_email": "[email protected]",
18 "created_at": "2024-06-23T10:25:00.000000Z"
19 },
20 {
21 "url": "31233453458b3989875fcc1a",
22 "product_type": "D-ID",
23 "product_name": "D-ID (video)⚡️",
24 "status": "waiting",
25 "payment_status": "complete",
26 "count": 1,
27 "price": "0.05",
28 "sum": "0.05",
29 "payment_type": "trx_usdt",
30 "payment_amount": "0.05",
31 "payment_c_date": "2024-06-23 09:15:00",
32 "discount": "0.00",
33 "product_description": "D-ID video generation account with 5$ balance",
34 "user_email": "[email protected]",
35 "created_at": "2024-06-23T09:10:00.000000Z"
36 }
37 ],
38 "pagination": {
39 "total": 25,
40 "limit": 100,
41 "offset": 0,
42 "has_more": false
43 }
44}
Filter Examples:
- By Status:
?status=completed
- By Payment Status:
?payment_status=complete
- By Date Range:
?created_at_from=2024-01-01&created_at_to=2024-12-31
- With Pagination:
?limit=50&offset=100
- Combined Filters:
?status=completed&payment_status=complete&limit=25
Status Values:
- Order Status: complete, waiting, success
- Payment Status: complete, waiting, success
Endpoint: https://autoreg.site/api/cancel_order
Cancel an existing order and process automatic refunds if fewer items were received than expected. The system will automatically calculate refunds based on the difference between ordered and received quantities, taking into account any applicable discounts.
Cancel Order Process:
- Validation: Order must exist, be paid, and created more than the required time interval ago
- Item Check: All order items are marked as checked and counted
- Refund Calculation: If fewer items received than ordered, automatic refund is processed
- Balance Update: Refund amount is added back to user balance
- Transaction Record: Refund transaction is recorded in order history
Request parameters | |||
---|---|---|---|
api_token | string | Required | Your api key |
order_url | string | Required | The unique order URL/identifier to cancel |
Response | |||||
---|---|---|---|---|---|
success | boolean | Operation success status | message | string | Response status message |
refund_amount | number | Amount refunded to user balance | received_count | integer | Number of items actually received |
expected_count | integer | Number of items originally ordered | order_url | string | The canceled order URL |
Examples:
CURL
1curl --location 'https://autoreg.site/api/cancel_order' \
2--header 'Content-Type: application/json' \
3--data '{
4 "api_token": "YOUR_API_TOKEN",
5 "order_url": "31234455665be28b3989875fcc1a"
6 }'
Response - Success with Refund
1{
2 "success": true,
3 "message": "Order canceled successfully",
4 "refund_amount": 0.02,
5 "received_count": 3,
6 "expected_count": 5,
7 "order_url": "31234455665be28b3989875fcc1a"
8}
Response - Success without Refund
1{
2 "success": true,
3 "message": "Order canceled successfully",
4 "refund_amount": 0,
5 "received_count": 5,
6 "expected_count": 5,
7 "order_url": "31234455665be28b3989875fcc1a"
8}
Response - Error (Order Not Found)
1{
2 "success": false,
3 "message": "Order not found, already processed or less than 10 minutes have passed since creation",
4 "refund_amount": 0,
5 "received_count": 0,
6 "expected_count": 0
7}
Response - Error (System Error)
1{
2 "success": false,
3 "message": "Error canceling order: Database connection failed",
4 "refund_amount": 0,
5 "received_count": 0,
6 "expected_count": 0
7}
Cancellation Rules:
- Time Requirement: Orders can only be canceled after 10 minutes
- Payment Status: Only orders with "complete" payment status can be canceled
- Order Status: Order must not already be in "complete" status
- Automatic Refund: If received quantity < ordered quantity, automatic refund is processed
- Discount Applied: Refund amount considers any discounts applied to the original order
How Refunds Work:
- Calculation: Refund = (ordered_count - received_count) × price_per_item
- Discount Application: If order had discount, refund is reduced by the same percentage
- Balance Update: Refund amount is immediately added to user balance
- Transaction Record: Refund creates a new "Balance Top-Up" transaction with payment_type "refund"
- Order Update: Original order quantities and amounts are updated to reflect actual received items