Change many addresses

POST 
/watch/addresses/bulk

Run one operation on up to 1,000 watched addresses:

• move to scenario_id: they follow the new scenario from now on, and only USDT that arrives after the move counts toward its threshold;
• pause_energy: no more Energy purchases; alerts and security alerts keep working, and the address keeps its place in the limit;
• resume: Energy purchases again, and a waiting deposit is picked up;
• remove: stop monitoring. The timeline stays for 90 days and the external ID is freed.

Each address gets a result in request order: ok (also when nothing had to change), not_found (not watched), limit_exceeded (move without room in the target's limit) or invalid (not a TRON address, or repeated in the request).

Request

Responses

200

Successful Response

401

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.

403

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.

404

radar_disabled, scenario_not_found. radar_disabled: TRONAgg Radar isn't available for this account.

422

invalid_op, empty_batch, batch_too_large, scenario_required (move without scenario_id). A body or parameter of the wrong type, or an unknown body field, returns FastAPI's detail array instead.

429

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

Retry-After

Seconds until the rate-limit window resets.