Get 辰汐ai Platform Order Details
Query an order by order ID. This endpoint supports two read modes: anonymous access returns only the minimal fields required by the payment page; the order owner returns full details when carrying an Account Token.
¶ API Overview
| Item | Content |
|---|---|
| Method | GET |
| URL | https://chens.platform.acedata.cloud/api/v1/orders/{order_id} |
| Authentication | Optional; anonymous is a minimal projection, authenticated owner is a full projection |
/orders/{id} and /orders/{id}/ are both currently available. The order ID is part of the payment link and should be treated as a sensitive opaque identifier; do not publicly distribute it.
¶ Anonymous Query
The payment page can read directly when the login state is lost:
export ORDER_ID='your order ID'
curl "https://chens.platform.acedata.cloud/api/v1/orders/${ORDER_ID}" \
-H 'Accept: application/json'
The anonymous response contains only id, description, price, state, pay_way, pay_url, expired_at, and created_at. It does not return account, Application, Package, internal payment identifiers, or metadata.
¶ Authenticated Query
export PLATFORM_TOKEN='your account token'
curl "https://chens.platform.acedata.cloud/api/v1/orders/${ORDER_ID}" \
-H 'Accept: application/json' \
-H "Authorization: Bearer ${PLATFORM_TOKEN}"
The order owner receives full Order details, including application / applications, package / packages, bank_details, invoice_automation, and model fields. If authenticated but not the order owner, 403 is returned; except for super administrators.
¶ Key Fields
| Field | Description |
|---|---|
state |
Pending, Paid, Finished, Expired, Failed, or Refunded |
pay_way |
The order's current payment method; the field name is not payment_method |
pay_url |
Hosted payment page or QR code URL; may be empty |
price |
The final amount payable for the order; the current order model does not provide a final_price field |
amount |
Package quota quantity; visible only in the authenticated full response |
finished_at |
Order completion time; the field name is not paid_at |
The full response may include additional fields depending on the payment method. Clients should read them as needed and always avoid logging sensitive metadata in the full response.
¶ Error Handling
404: The order ID does not exist.403: Logged in but not the order owner.- Anonymous requests do not return
401; they only receive the minimal public projection.
¶ Invoice Red Reversal and Reapplication
The order's current invoice can be retrieved through GET /api/v1/orders/{order_id}/invoice/. After an automatic red reversal is submitted, the invoice remains Issued, and red_state indicates the red reversal progress; successful submission does not mean the red reversal is complete. While waiting for confirmation, issuing a red invoice, or archiving, the order cannot apply for an invoice again.
When an administrator applies for a red reversal due to incorrect invoicing information such as the title or tax number, the reason for the red reversal is “Invoice Issued in Error”; automatic red reversals triggered by order refunds still use “Service Termination”.
After the red invoice is successfully issued and archived, the original invoice becomes Voided, and the order can apply again. The original invoice can be viewed in the invoice history. If the red reversal fails or its result is pending verification, it is handled by financial review, and the invoice application restriction for the order will not be lifted early. Manually issued invoices must first be voided or red-reversed in the tax or invoicing system, and then confirmed by finance on the platform.