Create a scenario
POST/watch/scenarios
Create a scenario: what Radar does for a group of addresses. Only name and action are required; every other field has a default.
action:alert_only(alerts only, never buys Energy),add_on_deposit(Energy for one transfer when deposits reachthreshold, default"100") oradd_after_transfer(Energy for the next transfer after each one that used Energy).threshold: counts USDT that arrives after the address joins the scenario and isn't swept yet. USDT already on the address doesn't count.energy_preset:65k(a recipient that already holds USDT, default),131k(any recipient) orcustomwithenergy_custom.energy_alerts: Energy warnings (address.energy.insufficient,address.trx.low). Omitted, they're off foralert_onlyand on for the Energy actions, which always warn.notify_destination_ids:nullsends to every channel (new ones included),[]keeps alerts in Radar, a list sends to those channels only.
Names are unique per account. Creating a scenario costs nothing: Energy is bought only when an address in it needs it.
Request
Responses
- 201
- 401
- 403
- 404
- 409
- 422
- 429
Successful Response
The X-API-Key header is missing, invalid or revoked. detail is a plain string: API key required, Invalid API key or User not found.
radar_access_required: the account has neither a Google sign-in nor 1 TRX of net confirmed deposits; required_deposit_sun and allowed_auth_methods say what unlocks it. The API-wide refusals also apply: a blocked account (plain-string detail) and ip_not_allowed.
radar_disabled. radar_disabled: TRONAgg Radar isn't available for this account.
scenario_name_taken: you already have a scenario with this name.
Input Radar can't accept, with field naming it: invalid_name, invalid_action, invalid_threshold, invalid_energy_preset, invalid_energy (custom Energy outside energy_min…energy_max), invalid_times_per_address_day, invalid_daily_budget (outside min_sun…max_sun), invalid_energy_alerts, invalid_active_hours, invalid_usdt_low_threshold, invalid_destinations (unknown lists channel ids that aren't yours). A body or parameter of the wrong type, or an unknown body field, returns FastAPI's detail array instead.
Rate limit exceeded: more than 1,000 requests per minute for your account (shared by all of its API keys and workspace sessions). detail is a plain string; wait the number of seconds in Retry-After, then retry.
Response Headers
Seconds until the rate-limit window resets.