Add addresses

POST 
/watch/addresses

Start watching up to 1,000 addresses in one scenario. Each item gets its own result, in the order you sent them, so one bad line never fails the batch:

• created: now watched;
• exists: already watched (in this scenario, or in another one with existing: "skip"); its scenario, label and external ID don't change;
• moved: was in another scenario and existing is "move";
• duplicate: the same address earlier in this request;
• invalid: error says why: invalid_address, invalid_label, invalid_external_id or external_id_taken;
• limit_exceeded: no room left in the scenario's limit. Items are admitted in request order.

summary counts each status. An add_on_deposit threshold counts USDT that arrives after the address joins the scenario and isn't swept yet. USDT already on the address doesn't count.

Radar alerts only on activity after an address is added.

Request

Responses

201

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

empty_batch, batch_too_large (more than 1,000 items; max), invalid_existing. 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.