Overview
Create one from Condor
Agents and the Condor chat use thecreate_dca_executor tool:
controller_id must be the session ID (see Session IDs).
Amounts here are in the quote asset, unlike the position executor, whose
amount is in the base asset. amounts_quote and prices are parallel lists: entry i is an order of amounts_quote[i] at prices[i]. Condor rejects lists of different lengths.Parameters
Modes
Levels are placed one after another, in the order ofprices. The next level is placed only after the previous level’s order exists.
Exits
Every exit cancels the unfilled levels and closes the filled amount with a market order.
Via the API
Create the executor withPOST /executors/. Unlike the position executor, the exits are top-level fields, not a triple_barrier_config.
activation_bounds, which the Condor tool doesn’t expose: a list of two fractions that controls when a level is placed. In TAKER mode it replaces the default 0.01% and 0.5%.
Close types
Besides the exits above, a DCA executor can end with:Stopping early
Stop the executor withstop_executor or POST /executors/{executor_id}/stop:
keep_position=false(the default) cancels unfilled levels and closes the filled amount at market.keep_position=truecancels unfilled levels and leaves the filled amount in the account.
Learn more
- Executors overview: lifecycle, close types and the API
- Position Executor: the whole position in one entry
- Grid Executor: repeated entries and exits across a range

