Binance Smart Money Tracker avatar

Binance Smart Money Tracker

Pricing

Pay per usage

Go to Apify Store
Binance Smart Money Tracker

Binance Smart Money Tracker

Query Binance Futures public leaderboard for top traders, open positions, or rolling performance. Writes one normalized dataset item per row.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

What this Actor does

Query Binance Futures public leaderboard for top traders, open positions, or rolling performance. Writes one normalized dataset item per row.

Input example

{
"mode": "top-traders",
"symbol": "BTCUSDT",
"period": "monthly",
"limit": 50
}

Input fields

Pick a query mode and (for trader-specific modes) provide a Binance encrypted user id. The Actor writes one normalized dataset item per leaderboard row.

  • mode (string, user input): top-traders returns the leaderboard. trader-positions returns open positions for traderUid. trader-performance returns rolling PnL/ROI/win-rate metrics for traderUid.
  • traderUid (string, user input): Binance encrypted user id. Required for trader-positions and trader-performance modes.
  • symbol (string, user input): Optional symbol filter (e.g. BTCUSDT).
  • period (string, user input): Rolling window for ranking and performance.
  • limit (integer, user input): Maximum rows to return for top-traders mode.
  • apiBaseUrl (string, optional override): Optional upstream API base URL override for local or staging QA.

Output dataset

Each successful upstream response is written to the default dataset.

  • input: Original input value submitted to the upstream API.
  • result: Full upstream API response.

Developer notes

Set BINANCE_SMART_MONEY_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push