Binance Copy Trading Leaderboard Scraper avatar

Binance Copy Trading Leaderboard Scraper

Pricing

from $4.99 / 1,000 results

Go to Apify Store
Binance Copy Trading Leaderboard Scraper

Binance Copy Trading Leaderboard Scraper

Scrapes the Binance Copy Trading leaderboard — top futures traders ranked by PnL or ROI with statistics like win rate, drawdown, AUM.

Pricing

from $4.99 / 1,000 results

Rating

0.0

(0)

Developer

Coding Frontned

Coding Frontned

Maintained by Community

Actor stats

0

Bookmarked

10

Total users

2

Monthly active users

0.27 hours

Issues response

8 days ago

Last modified

Share

What does Binance Copy Trading Leaderboard Scraper do?

This Actor collects the public Binance Copy Trading leaderboard from the Binance Copy Trading surface. It is a bounded Binance API alternative for public leaderboard research: it sends one unauthenticated public JSON request, keeps the returned records, and does not log in, use private endpoints, or fetch protected trader details.

The Actor is intentionally fail-closed. CAPTCHA, login, paywall, geofence, device-verification, WAF, rate-limit, and other access-denial responses stop the run immediately. A valid empty response or failed run leaves the dataset empty and writes sanitized machine-readable diagnostics to the OUTPUT key-value record.

Why use this Binance leaderboard scraper?

  • Collect public futures and copy-trading performance fields in a consistent dataset.
  • Rank by public PnL or ROI and select a public time range and portfolio filter.
  • Use the Actor with Apify scheduling, API access, webhooks, integrations, monitoring, and dataset exports.
  • Keep resource use predictable with one bounded response, a response cap of 18 records, timeout limits, bounded transient retries, request pacing, deduplication, and one ordered batch write.

The maxItems input is capped at 18 because this Actor makes only one bounded public request.

What data can this Actor extract?

FieldTypeDescription
rankintegerPosition in the returned public leaderboard response.
leadPortfolioIdstringPublic lead portfolio identifier.
nicknamestringPublic trader nickname.
portfolioTypestringPortfolio type returned by Binance.
portfolioFilterstringRequested ALL, SPOT, or FUTURES filter.
tradingModestringPublic Binance trading/API mode tag.
roinumberReturn on investment percentage.
pnlnumberProfit and loss in USDT.
copierPnlnumberAggregate public copier PnL.
aumnumberPublic assets under management in USDT.
mddnumberMaximum drawdown percentage.
winRatenumberWinning trade percentage.
currentCopiersintegerCurrent public copier count.
badgeUpdatedAtstringPublic badge update timestamp.
performanceHistoryarrayTyped public ROI chart points for the selected window.
profileUrlstringPublic Binance profile URL.
found / dataAvailablebooleanCountable-data status flags.

How to scrape the Binance Copy Trading leaderboard

  1. Open the Input tab and choose the ranking metric, time range, portfolio type, and desired item limit.
  2. Optionally adjust the bounded timeout, retry, and pacing controls.
  3. Click Start. The Actor requests one public leaderboard response and deduplicates repeated public portfolio IDs.
  4. Download the dataset or connect it to an Apify API, webhook, scheduler, or integration.

The Actor does not use a proxy to bypass a Binance access denial. The legacy proxyConfiguration field is accepted only so older input payloads remain valid; it is ignored.

How much does it cost to scrape Binance?

The Actor uses the pricing model shown on its Apify Store page. A run normally performs one bounded request and writes at most 18 public items. Review the Store pricing tab and your run usage before scheduling recurring workloads.

Input

See the input tab for full configuration options. The main fields are dataType (PNL or ROI), timeRange (7D, 30D, 90D, or 180D), portfolioType (ALL, SPOT, or FUTURES), and maxItems. requestTimeoutMs, maxRetries, retryDelayMs, and pacingMs are bounded numeric controls. Access-denial responses are never retried. proxyConfiguration is a deprecated compatibility field and has no effect.

Key-value store

The Actor writes OUTPUT for every completed or failed attempt. It contains status, data-availability flags, item counts, the applied filters, the 18-item response limit, and sanitized failure details when applicable. Diagnostics never pollute the dataset.

Output

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. A simplified countable output looks like this:

[
{
"rank": 1,
"recordType": "leaderboard",
"leadPortfolioId": "0000000000000000000",
"nickname": "Example Trader",
"portfolioType": "PUBLIC",
"portfolioFilter": "FUTURES",
"tradingMode": "API_KEY_TRADE",
"roi": 24.5,
"pnl": 12500.75,
"copierPnl": 3200.5,
"found": true,
"dataAvailable": true,
"source": "binance.com"
},
{
"rank": 2,
"recordType": "leaderboard",
"leadPortfolioId": "0000000000000000001",
"nickname": "Sample Strategy",
"portfolioType": "SIGNAL",
"roi": 18.2,
"pnl": 8300.25,
"found": true,
"dataAvailable": true,
"source": "binance.com"
}
]

Tips and advanced options

Use a small pacingMs value for scheduled workloads. Increasing maxRetries only helps transient network, timeout, or server errors; it cannot overcome a CAPTCHA, WAF, rate limit, geofence, or other denial. A valid empty result leaves the dataset empty and is explained in OUTPUT.

FAQ, disclaimers, and support

Does the Actor require a Binance login?

No. It uses only the public leaderboard surface evidenced by the Actor source. It does not request credentials, tokens, signatures, private APIs, or protected sessions.

Why did my run stop without dataset items?

The endpoint may have returned no public records or an access-denial/challenge response. Inspect the OUTPUT record and run log, and respect Binance and Apify limits; the Actor does not bypass those controls.

Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

For feedback, use the Issues tab. Use the API tab for programmatic access and the Apify monitoring tools for operational alerts.