Field formats

Numeric values in requests

Traffic values in requests are expressed in GB and sent as plain decimal strings with up to six decimal places:

{
  "traffic_gb": "100.000000"
}

Traffic request fields in this API version do not accept scientific notation, negative numbers, NaN, or infinite values. Whether 0 is allowed depends on the relevant API article. Integer request fields must use JSON integers, not quoted strings.

Amounts and unit prices in responses

Amounts and unit prices are returned as decimal strings. Amounts always contain four decimal places, and unit prices always contain six:

{
  "order_amount": "12.5000",
  "unit_price": "0.850000"
}

Do not store or calculate amounts and unit prices with binary floating-point types.

Traffic values in responses

Traffic values in responses always contain six decimal places:

{
  "traffic_gb": "100.000000",
  "adjusted_traffic_gb": "-1.250000"
}

adjusted_traffic_gb is the cumulative adjustment and may therefore be negative. See the relevant API article for the meaning and range of other fields.

Time values

Timestamps use GMT+8 ISO-8601 strings with an explicit offset, for example:

2026-08-24T15:30:00.000+08:00

Filter parameters must include Z or an explicit time-zone offset. Date fields use yyyy-MM-dd calendar dates in Asia/Shanghai, for example 2026-08-24.

Boolean values

Boolean fields use the JSON values true or false. Do not send the string "true" or the numbers 1 and 0.

IDs and order numbers

Treat resource IDs, account IDs, and order numbers as strings. Even when they contain digits only, do not convert them to types such as JavaScript Number that may lose precision.