Support and troubleshooting

Updated: 2026-10-19. https://tronhooks.com/docs/support/

Contact ops@tronhooks.com for integration help, security reports or account-data requests. Include a UTC timestamp, the relevant event/watch ID and a redacted error. Never include API keys, session cookies, passwords, webhook secrets or wallet recovery phrases.

No alert arrived

1. Check service status and whether the chain transfer is finalized.
2. Confirm mainnet, the watched address, USDT/TRX asset and incoming/outgoing direction. New watches do not backfill earlier transfers.
3. For Telegram, check that the account is connected and the bot has not been blocked. Do not reconnect someone else's chat.
4. For webhooks, inspect your receiver status, raw-body signature verification and timeout. Read retry and dead-letter guidance.
5. List events in the console or API. A DEAD delivery means retries failed, not that the blockchain transfer failed. Reconcile before taking an accounting action.

A safe support request

Describe the expected behavior, the observed behavior, time window and any error code. If the URL contains credentials or identifying parameters, redact it. Routine diagnosis uses logs and offline fixtures. Sending a real test message is a separate action that needs your agreement.

For balance-snapshot or low-balance requirements, send the asset, required threshold semantics and expected frequency to support. Do not send credentials or private keys. These capabilities are not currently supported.

Markdown · Capabilities JSON