Reseller API Documentation
Place orders programmatically by tag_line. Orders are charged to your wallet balance â how each package is actually fulfilled behind the scenes is never something you need to worry about.
Authentication
Every request must include your api_key as a field in
the request body (JSON for POST, query string for GET). Your key is auto-issued at
registration and visible on your dashboard.
{
"api_key": "AMz-XXXXXXXXXXXXXXXXXXXXXXXX",
...
}
https://amzapi.aurponff.com/api
Every successfully placed order deducts its price from your wallet balance. If your
balance is too low, the order is rejected with 402 Payment Required.
Keep your API key secret â anyone with it can place orders that draw from your wallet.
Packages
Every orderable package has a tag_line â that's the
identifier you send in the API, not the package name. Prices are charged to your wallet balance.
25 Diamond
25
50 Diamond
50
Weekly Lite
LITE
Level Up 6
LV6
Level Up 15
LV15
Level Up 20
LV20
Level Up 25
LV25
Level Up 10
LV10
115 Diamond
115
Level Up 30
LV30
240 Diamond
240
Weekly
WEEKLY
610 Diamond
610
Full Level Up Pass
LVFULL
Monthly
MONTHLY
1240 Diamond
1240
2530 Diamond
2530
Place an Order
/api/resale-order
| Field | Required | Description |
|---|---|---|
| api_key | Yes | Your account's API key |
| account_info.player_id | Yes | Free Fire player UID |
| selectedPackage.tag_line | Yes* | Package identifier â *or use items[] below |
| quantity | No | Default 1 |
| order_id | Yes | Your own unique order reference |
| url | No | Webhook URL for the final result |
curl -X POST https://amzapi.aurponff.com/api/resale-order \
-H "Content-Type: application/json" \
-d '{
"api_key": "AMz-XXXXXXXXXXXXXXXXXXXXXXXX",
"account_info": { "player_id": "123456789" },
"selectedPackage": { "tag_line": "100" },
"quantity": 1,
"order_id": "YOUR-REF-0001",
"url": "https://your-store.com/webhooks/topup"
}'
{
"message": "Order Placed Successfully",
"order": {
"id": 10234,
"order_id": "YOUR-REF-0001",
"status": "pending",
"payment": "complete",
"package_name": "100 Diamonds",
"sale_price": 95,
"qty": 1,
"content": null
}
}
Order Multiple Packages
Same endpoint â send an items array instead of
selectedPackage + quantity.
You can freely mix ANY of your packages in one request â how each one is actually fulfilled
behind the scenes is entirely our own business; you only ever deal in tag_line.
{
"api_key": "AMz-XXXXXXXXXXXXXXXXXXXXXXXX",
"account_info": { "player_id": "123456789" },
"items": [
{ "tag_line": "100", "quantity": 1 },
{ "tag_line": "200", "quantity": 2 }
],
"order_id": "YOUR-REF-0001",
"url": "https://your-store.com/webhooks/topup"
}
When every item in the request settles cleanly you'll still get the single
order shape shown above for a single item, or an
items array (below) once more than one item is involved â
each entry uses the exact same fields either way, so you only need to write one parser:
{
"message": "Order Placed Successfully",
"items": [
{
"order_id": "YOUR-REF-0001",
"tag_line": "100",
"status": "complete",
"payment": "complete",
"package_name": "100 Diamonds",
"sale_price": 95,
"qty": 1,
"content": null
},
{
"order_id": "YOUR-REF-0001",
"tag_line": "200",
"status": "complete",
"payment": "complete",
"package_name": "200 Diamonds",
"sale_price": 180,
"qty": 2,
"content": null
}
]
}
status is "complete" or
"cancel" per item â check each one individually rather than
only the top-level HTTP status, since a mixed request can partially succeed
(HTTP 207). You're only ever charged for items that
actually completed.
Check Order Status
/api/resale-order/status
curl "https://amzapi.aurponff.com/api/resale-order/status?api_key=AMz-XXXXXXXXXXXXXXXXXXXXXXXX&order_id=YOUR-REF-0001"
Works for any order regardless of which package/provider fulfilled it â you never need to know or track that yourself.
Webhooks
If your order's final result isn't known immediately, the result is POSTed directly to the
url you supplied once it completes or fails:
{
"orderid": "YOUR-REF-0001",
"status": "success",
"content": "ABCD-EFGH-1234",
"codes": []
}
Most orders resolve synchronously and you'll already have the final result in the API
response itself â url is a safety net for the rare case
where it doesn't. Either way, Check Order Status
always reflects the true current state.