auto_orders array of a
swap request. Each order is evaluated after the parent
trade lands and sells part or all of your position when it triggers.
Omitted, empty, or explicit
Bloom users configure a default Spot strategy in Bloom Manager — the take-profits, stop-losses, and dev-sells the bot and extension attach to every trade. The API applies it the same way, and lets you opt out per swap:
So an integration that wants Bloom to behave as it does everywhere else simply
leaves the field out, and one that manages exits itself sends
[].
Fields
All numeric fields are JSON numbers, not strings.
priority_fee and processor_tip are denominated per host, exactly as they are
on the parent swap — see Fee denomination.
What target_value means
The same target_value field is interpreted differently for each target_type:
To create an automatic dev-sell, set
target_type to dev_sell. There is no
separate flag — the trigger type is the only thing you set.Limits
You can attach up to 20 auto-orders to a swap. Any beyond 20 are dropped.Examples
Take-profit at +50%
Sell the entire position when the price is up 50% from entry:Stop-loss at -20%
Sell the entire position when the price is down 20% from entry (a negativetarget_value is a stop-loss):
Dev-sell
Exit when the token creator sells.target_value: 0 triggers on any dev sell;
100 triggers only on a full (whole-position) dev sell:
Attaching auto-orders to a swap
Add the orders to theauto_orders array of a buy. This example takes profit at
+50% and also exits if the creator sells:

