New Listed Crypto Coins Scraper

Scrape newly listed crypto coins and token listings into a clean JSON dataset for alerts, dashboards, discovery workflows, and research.

This Actor is focused on new crypto listings only. It is built for users who want a search-friendly, simple feed of newly listed crypto coins without mixing in gainers, losers, trending pages, or other leaderboard categories.

What This New Crypto Listings Scraper Extracts

This actor is configured to scrape the New Listings page only.

It extracts newly listed crypto coins into a normalized dataset so you can track fresh listings, trigger notifications, or feed downstream automation.

Why Use This Actor

• Scrapes new listed crypto coins only, without unrelated leaderboard pages
• Returns normalized listing data in a simple dataset shape
• Works well for crypto alerts, new token discovery, and listing monitors
• Uses fast HTTP parsing instead of a heavy browser flow
• Includes Apify dataset and output schemas for cleaner Console output

Common Use Cases

• Track newly listed crypto coins every hour or every day
• Build a new token monitoring dashboard
• Send alerts for fresh listings to Telegram, Discord, or Slack
• Feed newly listed coin data into research or ranking pipelines
• Monitor new crypto listings before they gain wider visibility

Input

The Apify Console uses a locked dropdown selector named pageSelection.

Available option:

• New Listed Crypto Coins

Example local input:

{
	"pageSelection": "new"
}

Output Dataset

Each dataset item is a normalized CoinMarketCap leaderboard row with fields such as:

• sourcePage
• sourceUrl
• section
• position
• coinId
• name
• symbol
• slug
• coinUrl
• rank
• priceUsd
• marketCapUsd
• volume24hUsd
• priceChange1h
• priceChange24h
• priceChange7d
• priceChange30d
• addedDate
• platforms
• scrapedAt

Sample output item:

{
	"sourcePage": "/new",
	"sourceUrl": "https://coinmarketcap.com/new/",
	"section": "new",
	"position": 1,
	"coinId": 12345,
	"name": "Example Coin",
	"symbol": "EXM",
	"slug": "example-coin",
	"coinUrl": "https://coinmarketcap.com/currencies/example-coin/",
	"rank": 250,
	"priceUsd": 0.0123,
	"marketCapUsd": 4567890.12,
	"volume24hUsd": 987654.32,
	"priceChange24h": 42.5,
	"priceChange7d": 88.1,
	"scrapedAt": "2026-03-16T12:00:00.000Z"
}

The Actor also includes .actor/output_schema.json and .actor/dataset_schema.json so the Apify Output tab is easier to scan.

How To Run

Run locally with Apify CLI:

$apify run

For local development, place input in storage/key_value_stores/default/INPUT.json.

Deploy to Apify:

apify login
apify push

Pay Per Event

This Actor is PPE-ready in code and pushes dataset items through Actor.pushData(..., 'new-listing-item').

The repository includes .actor/pay_per_event.json with the PPE event definitions used by this Actor.

Recommended Apify monetization setup:

• Keep the synthetic apify-actor-start event enabled
• Use new-listing-item as the primary custom event
• Price each event based on the value of one normalized leaderboard row

The actual pricing model is configured through Apify monetization settings, while the local PPE event definitions live in .actor/pay_per_event.json.

For local PPE validation:

$env:ACTOR_TEST_PAY_PER_EVENT='true'
$env:ACTOR_USE_CHARGING_LOG_DATASET='true'
apify run

FAQ

Does this scrape live CoinMarketCap leaderboard pages?

Yes. It fetches the current HTML and parses CoinMarketCap's server-rendered Next.js payloads at run time.

Which pages are supported?

This actor is currently configured for new crypto listings only.

Does this require Playwright or a browser?

No for the current supported pages. The Actor uses a faster HTTP parsing approach for the main flow.

Who is this Actor for?

Crypto researchers, traders, data engineers, dashboard builders, and automation workflows that need CoinMarketCap leaderboard data in a clean JSON format.

Notes

• Respect CoinMarketCap terms and your own compliance requirements when using scraped data
• Pricing, page structure, and extracted fields can change when the source site updates
• If you want to add more listing or leaderboard pages later, extend the page map and extraction logic in src/main.ts