TSUN TOKEN FETCHER

SYSTEM IDLE | LAST RUN: NEVER

Success Rate

0 tokens fetched

Failed Attempts

0 errors logged

Performance

0.0 req/sec

API Load Distribution

🔵 API-1: -
🟣 API-2: -
🟠 API-3: -

System Console

Establishing secure connection...

Execution History

0 runs
📊

No historical data found

Execute a token refresh to see history
🟢

SYSTEM HEALTHY

Last Check: --:--:--

📦 ENVIRONMENT

Mode --
Python Version 3.10.x
Platform --

⚙️ CONFIGURATION

Concurrent Requests --
Max Retries --
Account Timeout --

🔗 GITHUB INTEGRATION

Status --
Repository --
Storage Path --

🌐 API ENDPOINTS

📚 API DOCUMENTATION

GET POST /api/run

Trigger the token fetch operation. In serverless mode, this will wait for completion. In local mode, it starts a background job.

GET /api/status

Get the current execution status, including progress, stats, and environment information.

GET /api/logs

Stream live logs using Server-Sent Events (SSE) in local mode, or get recent logs as JSON in serverless mode.

GET /api/history

Retrieve the execution history of the last 10 runs.

CRON SETUP

To automate token refreshing, set up a cron job (e.g., using GitHub Actions or EasyCron) to call the run endpoint:

https://yourlink.com/api/run

Recommended Schedule: Every 6 hours

0 */6 * * *