Hi Aster team,
We are integrating Aster as a third-party trading frontend and following the official recommendation to use V3 APIs for new integrations.
However, we found several feature gaps between the official Web frontend and the documented public V3 API surface.
- Native TWAP support
The official Aster Web trading UI supports TWAP orders on futures markets. From the Web frontend behavior, TWAP appears to be implemented through private Web BAPI endpoints such as:
- /bapi/futures/v3/private/future/twap/place-twap
- /bapi/futures/v3/private/future/twap/close-twap
- /bapi/futures/v1/private/future/twap/query-open-twaps
- /bapi/futures/v1/private/future/twap/query-twap-history
- /bapi/futures/v1/private/future/twap/query-twap-sub-orders
But the public Futures V3 documentation does not seem to expose equivalent TWAP place/cancel/query endpoints.
Question:
Is native TWAP officially supported for third-party V3/API-wallet/agent integrations? If yes, could you document the V3 endpoints, request parameters, signing requirements, and response schema? If not, could you explicitly mark TWAP as unsupported in public V3?
- Missing account analytics / PnL statistics
The official Web frontend can display account-level statistics such as PnL and other portfolio/account analytics through private BAPI endpoints. But the documented V3 APIs do not seem to provide equivalent endpoints for third-party frontends to retrieve the same data.
Question:
Is there a public V3-supported way to fetch account PnL/statistics equivalent to the official Web UI? If yes, could you document the endpoints and schemas? If not, could you confirm whether these analytics endpoints are planned for V3?
Why this matters:
Third-party trading frontends should not rely on undocumented private Web BAPI endpoints because their authentication/session model and stability guarantees are unclear. Since V3 is recommended for new integrations, these Web-only capabilities create feature parity gaps for integrators.
Thanks.
Hi Aster team,
We are integrating Aster as a third-party trading frontend and following the official recommendation to use V3 APIs for new integrations.
However, we found several feature gaps between the official Web frontend and the documented public V3 API surface.
The official Aster Web trading UI supports TWAP orders on futures markets. From the Web frontend behavior, TWAP appears to be implemented through private Web BAPI endpoints such as:
But the public Futures V3 documentation does not seem to expose equivalent TWAP place/cancel/query endpoints.
Question:
Is native TWAP officially supported for third-party V3/API-wallet/agent integrations? If yes, could you document the V3 endpoints, request parameters, signing requirements, and response schema? If not, could you explicitly mark TWAP as unsupported in public V3?
The official Web frontend can display account-level statistics such as PnL and other portfolio/account analytics through private BAPI endpoints. But the documented V3 APIs do not seem to provide equivalent endpoints for third-party frontends to retrieve the same data.
Question:
Is there a public V3-supported way to fetch account PnL/statistics equivalent to the official Web UI? If yes, could you document the endpoints and schemas? If not, could you confirm whether these analytics endpoints are planned for V3?
Why this matters:
Third-party trading frontends should not rely on undocumented private Web BAPI endpoints because their authentication/session model and stability guarantees are unclear. Since V3 is recommended for new integrations, these Web-only capabilities create feature parity gaps for integrators.
Thanks.