Static IP Renewal Order Creation
Create a renewal order for the specified proxy IP, supporting pure wallet payment, online payment and mixed payment. Only static residential IPs and static datacenter IPs support renewal and auto-renewal; dynamic IPs are not applicable.
Interface Address:
/papi/order/ip/renewal/createRequest Method:
POSTContent-Type:
application/jsonHeader Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| X-Access-Key | string | Yes | API access key ID. See API Rules for authentication |
| X-Signature | string | Yes | Signature value, Base64-encoded HMAC-SHA256 result |
| X-Timestamp | string | Yes | Millisecond-level Unix timestamp (13 digits) |
| X-Nonce | string | Yes | Random string, 10~32 lowercase letters and digits |
Body Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| uid | string | Yes | UID of the proxy IP |
| packageCode | string | Yes | Renewal package code |
| payCode | string | Yes | Payment method code; WALLET for pure wallet payment, actual code for online payment |
| providerCode | string | Yes | Payment provider code; INTERNAL for wallet payment |
| autoRenew | integer | No | Auto-renewal setting: 0 disabled, 1 enabled; current setting is kept when omitted |
| walletPayAmount | long | No | Wallet payment amount for mixed payment, in cents; must be greater than 0 and less than the order's actual payment amount |
Request Example:
{
"uid": "actual proxy IP uid",
"packageCode": "actual package code",
"payCode": "WALLET",
"providerCode": "INTERNAL",
"autoRenew": 1
}Response Parameters:
| Parameter | Type | Description |
|---|---|---|
| code | integer | Error code. See Error Codes |
| data | object | Return data |
| ├─ orderNo | string | Associated order number |
| ├─ payAmount | long | Order actual payment amount, in cents |
| ├─ walletPayAmount | long | Wallet payment amount, in cents |
| ├─ onlinePayAmount | long | Online payment amount, in cents |
| ├─ payUrl | string | Payment URL provided by the channel |
| ├─ paymentStatus | integer | Payment status |
| ├─ fulfillmentStatus | string | Fulfillment status |
| msg | string | Error message |
Response Example:
{
"code": 0,
"data": {
"orderNo": "",
"payAmount": 0,
"walletPayAmount": 0,
"onlinePayAmount": 0,
"payUrl": "",
"paymentStatus": 0,
"fulfillmentStatus": ""
},
"msg": ""
}Notes:
- For mixed payment, pass the actual online
payCode,providerCodepluswalletPayAmount; the online amount is calculated by the backend.payParamscan be passed per channel. - If the IP has no auto-renewal policy yet, an explicit
autoRenewcreates a policy under the existing renewal rules. - Auto-renewal policies can also be managed via Update Auto-Renewal Switch.
Wallet payment rules
Wallet payment uses payCode=WALLET and providerCode=INTERNAL. Mixed payment uses the actual online channel plus an integer walletPayAmount in USD cents, greater than zero and below the calculated payable total; do not submit onlinePayAmount. Recharge orders cannot use wallet or mixed payment. On timeout or uncertain payment status, query the original order and transactions before retrying. Cancellation or switching to wallet payment requires reliable confirmation that an existing online payment is closed. Wallet deductions are returned against the original transaction when cancellation is permitted.
