Static proxy renewal workflow

Static proxy renewals enter asynchronous processing after the order is accepted and payment succeeds. One request may renew 1–500 deduplicated resources. All resources use the same renewal duration, but individual resource outcomes may differ.

sequenceDiagram
    participant C as Caller
    participant A as Open API
    participant W as Callback receiver

    C->>A: List static proxy resources
    A-->>C: Return resource IDs and expiration times
    C->>A: Create renewal order (resources, common duration, request_no, optional callback_url)
    A-->>C: Payment succeeds; return PROCESSING and order number
    par Automatic polling
        loop While order is PROCESSING
            C->>A: List renewal orders by order number
            A-->>C: Return order status
        end
    and callback_url was provided
        A->>W: Notify once on first transition to COMPLETED or FAILED
        W-->>A: Return any 2xx response
    end
    C->>A: List renewal orders by order number
    A-->>C: Return latest order status
    C->>A: List static proxy resources
    A-->>C: Return latest expiration times

Integration steps

1. Call List static proxy resources, then select IDs that are currently ACTIVE and have not expired.
2. Select one duration for the entire order: all-ISP orders support 7 and 30 days; all-ISP_NATIVE orders support 7, 30, and 90 days; mixed orders support 7 and 30 days.
3. Call Create a static proxy renewal order directly, and save the returned order_no. The endpoint checks resource status and calculates the order amount using the price in effect when the order is placed.
4. Call List static proxy renewal orders every 10–30 seconds, filtering by the exact order_no. Stop polling when the order is COMPLETED; if it is FAILED, stop automatic polling and contact customer support.
5. Call List static proxy resources again, match the submitted resource IDs in the paginated results, and read their latest expiration times.

For a COMPLETED order, order-level finish_time is the time when all resources completed. For a FAILED order, resources that renewed successfully retain their new expiration times.

A callback is sent only once, when the order first enters COMPLETED or FAILED, and failed delivery is not retried. FAILED orders are not refunded automatically. After support completes manual handling, query the renewal-order list and static proxy resources again for the latest result.

Creation error 300320 means that the resource price does not exist or does not match the requested specification. The actual msg follows X-LANG; if omitted or unsupported, en_US is used.