> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acedata.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Refresh AceDataCloud Platform Order Status

> Platform integration guide - Ace Data Cloud

Actively query the latest status of the payment method corresponding to the order and synchronize it to the platform. This request may access the payment service and change the order status; use it only when callbacks are delayed or immediate confirmation is required.

## Preparations

* Use an [Account Token](https://platform.acedata.cloud/documents/platform-token).
* Obtain your order ID from the [order list](https://platform.acedata.cloud/documents/platform-order-list).

```shell theme={null}
export PLATFORM_TOKEN='your account token'
export ORDER_ID='your order ID'
```

## API Overview

| Item | Content |
| - | - |
| Method | `POST` |
| URL | `https://platform.acedata.cloud/api/v1/orders/{order_id}/refresh/` |
| Authentication | Order owner or super administrator |
| Body | Usually empty; the PayPal callback scenario may require `payer_id` / `PayerID` |

```shell theme={null}
curl -X POST \
  "https://platform.acedata.cloud/api/v1/orders/${ORDER_ID}/refresh/" \
  -H "Authorization: Bearer ${PLATFORM_TOKEN}"
```

A successful response returns the complete refreshed Order object. Use `state` to determine the result, and use `finished_at` as the completion time; the current model does not have a `paid_at` field. Status values include `Pending`, `Paid`, `Finished`, `Expired`, `Failed`, and `Refunded`.

The payment deadline will only change orders still in `Pending` to `Expired`. Refunded `Refunded` orders remain refunded after refresh or after receiving delayed payment callbacks.

## Retry Recommendations

* For normal payments, rely on platform callbacks first; actively refresh only when the status is not updated for a long time.
* Do not use fixed high-frequency polling. Exponential backoff is recommended, and stop after a clear final state.
* `401` indicates an invalid token; `403` indicates that you are not the order owner; `404` indicates that the order does not exist.
* When the payment service query fails, retain the order ID and trace ID and retry later; do not create duplicate orders as a substitute for status confirmation.

## Related APIs

* [Get Order Details](https://platform.acedata.cloud/documents/platform-order-detail)
* [Pay for an Order](https://platform.acedata.cloud/documents/platform-order-pay)
* [Get Order List](https://platform.acedata.cloud/documents/platform-order-list)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.