Resellers can use the unified API to sync catalogs, create orders, and track progress. Public documentation does not include API keys; orders are paid from your account balance. Store your API keys on the server side.
Service sync and ordering
Call services to get the service ID, price per thousand, minimum and maximum quantities, refill tags, and link format.
Fill in the public page or specified content link based on the service type, then submit via add. The order will re-validate quantity, link, and balance.
Save the returned AQNAB order ID, then call status to see the actual synced status, start count, and remaining count.
If a request times out or results are uncertain, first check the order and verify manually. Do not switch to another route and resubmit directly. Only after confirming the order was not accepted should you choose another service and resubmit.
Minimal call example
curl -X POST https://aqnab.com/api/v2 -d 'key=YOUR_API_KEY' -d 'action=services'
API: POST /api/v2; accepts form or JSON, returns JSON. Balance query action=balance; order placement action=add, pass service, link, quantity; progress query action=status, pass order. For custom comments, also pass comments; for keyword services, also pass keywords.
Refill, cancellation, and sub-site purchasing
status supports orders batch query (up to 100 orders); refill accepts order or orders, refill_status accepts refill or refills; cancel accepts orders. Refills and cancellations are only accepted when the service supports them; requests enter an asynchronous queue, and a cancellation request does not mean a refund has been issued.
Each sub-site API access page provides a separate secret key. Sub-site keys use the purchase balance you preloaded on that supplier site and place orders at that site's rates; they do not use balances from other sites or the main site. If the purchase balance at any level is insufficient, the entire deduction is rejected. Customer recharges go to the receiving account configured for that supplier site.
Blog posting, directory, and image API
The agent publish API supports creating drafts, previewing, editing, publishing, listing, and deleting. It uses a separate publish key and can be restricted to the main site or a specific sub-site. Test drafts before publishing final articles.
Get the service ID and current account price from the service catalog, then use the same key to place and check orders.
HTTP method
POST
API endpoint
https://aqnab.com/api/v2
Request format
JSON or form (application/x-www-form-urlencoded)
Response format
JSON · Pricing unit USD
Verification method
Send in request bodykey. The key is stored only on the server.
Request refill refill
Only orders marked refill=true and already submitted to the upstream are supported. Requests enter a queue first; if the supplier's response is unclear, wait for verification and do not resubmit. You can batch up to 1–100 order numbers in the orders field.
Parameters
Type
Description
key
String
Required. Your AQNAB API Key.
action
String
必填。固定为 refill。
order
String
Single order ID; for batch use orders, comma-separated.
Only non-final orders with cancel=true are supported. A return of 1 means the request is queued, not that it is canceled or refunded. Continue checking the order status.
Returns the sales catalog available to the current account. Use the service string to place orders; rate is the USD selling price per 1,000 units. When required appears, pass order parameters according to that list. The refill/cancel flags indicate whether the product supports refill and cancellation requests.
Returns the available balance of the account associated with the current API key. The balance is a string with 4 decimal places.
Parameters
Type
Description
key
String
Required. Your AQNAB API Key.
action
String
必填。固定为 balance。
Request body (JSON)
{
"key": "YOUR_KEY",
"action": "balance"
}
Success Response Example
{
"balance": "12.5000",
"currency": "USD"
}
Create Order add
Create a real order and deduct the balance. Total amount = quantity ÷ 1,000 × current price per thousand, rounded to four decimal places. Save the order number after receiving it for later queries. If the request times out, first check the order in the console to avoid duplicate submissions.
Parameters
Type
Description
key
String
Required. Your AQNAB API Key.
action
String
必填。固定为 add。
service
String
Required. Use the service ID returned by services, e.g., AQ1-123.
link
String
Required. A publicly accessible http or https target link.
quantity
Integer
Required for standard services, must be between min and max. Custom reviews are counted by valid lines.
comments
String
Custom comments are required, one per line, up to 20,000 characters total; blank lines do not count toward the quantity.
keywords
String
Required for services that ask for a custom keyword, up to 2,000 characters; not needed for other services.
You can only query orders for the current account. Pass orders to batch query up to 100 orders (comma-separated); batch results are indexed by order ID. Statuses include Pending, In progress, Completed, Partial, Canceled. start_count and remains come from upstream status sync; they are null until returned. Upstream status is not independent proof of actual delivery.
Parameters
Type
Description
key
String
Required. Your AQNAB API Key.
action
String
必填。固定为 status。
order
String
Required. The order field returned when creating the order.
Invalid parameters, service unavailable, or insufficient balance.
401
Key is invalid or has been revoked.
404
No orders found for this account.
500 / 502
Service temporarily unavailable. If an order request fails, check your orders and balance first.
Error Response Example
{
"error": "Insufficient funds"
}
cURL form example
curl -X POST https://aqnab.com/api/v2 \
--data-urlencode "key=YOUR_KEY" \
--data-urlencode "action=services"
登录后管理下单密钥. The publish key is generated independently by the site owner in the SEO optimization section and handed over securely.
FAQ
What operations can the API perform?
The current /api/v2 supports services, balance, add, and status. Service sync reads current retail prices and ranges, add creates real paid orders, and status queries progress after upstream sync.
Can I switch services immediately after a timeout?
No. A timeout may mean the order was already accepted; you must first check the original order and manually verify before deciding to create a new order. The current system will not automatically switch routes and repurchase when the submission result is uncertain.
How do I get an API key?
After logging in, generate an order key in the API Access Center based on your account conditions. Blog publishing uses a separate publishing key, which can be restricted to specific reseller panels and cannot be used to place paid orders.
Can agents publish blogs directly?
You can use the publishing API to create drafts, then update to published after confirming the preview; it supports listing, modifying, deleting, and image uploads. See the API documentation for full fields and rate limits.
Why can't service IDs be replaced arbitrarily?
Each service ID corresponds to a specific service and route; price, target link, range, and after-sales may all differ. Sync the catalog first, then submit using the returned ID and link format—do not guess the number.