Close all positions by account in Tradematic Cloud
A documented Tradematic Cloud operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Close all positions by account
- POSTChanges data · Cloud API
api.tradematic.com/cloud/accounts/{accountid}/closeall
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Tradematic Cloud operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Tradematic Cloud operations
- Create a new taskPOST · changes data
- Register a new userPOST · changes data
- Create new API keyPOST · changes data
- Create a new connectionPOST · changes data
- Create new autofollow strategyPOST · changes data
- Place a new orderPOST · changes data
- Logs user into the systemPOST · changes data
- Send a new signal for autofollow strategyPOST · changes data
Questions
- Can HumDay close all positions by account in Tradematic Cloud?
- Yes. This operation is published in Tradematic Cloud's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Tradematic Cloud data?
- Yes — this is a POST operation, so it changes something in Tradematic Cloud. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Tradematic Cloud account.
Where this came from
Read from a published API description for Tradematic Cloud at tradematic.cloud/sdk/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.