API Specification - Wrong Comments

[403access]

Hello,

there is an error in the comments of the Trade History API specification.

Since unfortunately the API specification is not available on GitHub,
or at least I couldn't find it, this issue is created.

https://docs.kraken.com/api/docs/rest-api/get-trade-history

Property cvol within the trade object suffers from a copy & paste error
coming from the property cfee above:

Total fee of closed portion of position (quote currency)
Only present if trade opened a position

---

Besides of that, sometimes an attribute is typed as integer,
integer<int64> and number.

Differentiating between 32bit and 64bit data types seems convenient
for developers. number in turn is confusing if those other types exist.

Thank you for such an amazing exchange and have a great day!

Best regards,
403access

[claudeenriquez]

Hey @403access, thanks for reaching out!

We’re planning to publish the OpenAPI specs on GitHub soon :)

To clarify:

• number is used for floating-point values (i.e., numbers with decimals).
• integer is used for whole numbers without decimals.

You can also find this distinction explained in Swagger’s OpenAPI guide.