🐧 OpenSea NFT Scraper

OpenSea NFT Scraper extracts structured NFT collection data, NFT metadata, traits, images, and collection statistics from OpenSea using collection URLs or collection slugs.

Use it for NFT research, collection analysis, dataset building, automation, APIs, spreadsheets, and data pipelines without manually browsing OpenSea.

• 🖼 Collect NFT metadata: token IDs, names, descriptions, images, metadata URLs, and OpenSea asset links
• 📊 Analyze collection statistics: floor price, total volume, total sales, and owner count
• 🧬 Extract NFT traits: structured trait arrays plus CSV-friendly text
• 🔗 Preserve collection context: collection name, slug, category, image, URL, and contract
• 📄 Clean Dataset output: one NFT is stored as one Apify Dataset row
• 🔁 Automatic pagination: request hundreds of NFTs without manually handling cursors
• ⚡ Automation-ready: use the Dataset through Apify API, exports, and integrations

---

📦 What data does OpenSea NFT Scraper extract?

🖼 NFT image	🆔 Token ID
🏷 NFT name	📝 NFT description
🔗 OpenSea NFT URL	📜 Contract address
⚙️ Token standard	🧬 NFT traits
🧾 Traits text	🔗 Metadata URL
🎞 Animation URL when available	💵 Estimated USD value when available
🚫 Disabled status	🔞 NSFW status
🕒 NFT update timestamp	🐧 Collection name
🔎 Collection slug	🔗 Collection URL
🖼 Collection image	🏷 Collection category
Ξ Floor price	💱 Floor currency
📈 Total collection volume	💱 Volume currency
🧾 Total collection sales	👥 Owner count
➡️ Has next page	🔁 Next cursor
🕒 Scrape timestamp	📥 Original collection reference

Missing fields are returned as null when OpenSea does not provide them. The Actor does not invent NFT or collection data.

---

🚀 Features

OpenSea NFT Scraper is designed for NFT collection extraction and normalized NFT datasets.

• Collection URL or slug input
• Multiple collections in one run
• Up to 1,000 NFT items per collection
• Automatic cursor pagination
• One NFT per Dataset row
• Collection statistics repeated on every NFT row for easy exports
• Raw structured NFT traits
• CSV-friendly traitsText
• NFT and collection image URLs
• OpenSea NFT and collection links
• Predictable normalized Dataset schema
• Partial failure protection between collections
• Apify API-friendly output
• HTTP/API-first architecture without browser automation for the normal collection workflow

---

⬇️ Input

You can configure OpenSea NFT Scraper directly from the Apify Console or send input programmatically through the Apify API.

🐧 OpenSea collection URLs or slugs

Use either a collection slug:

pudgypenguins

or a full OpenSea collection URL:

https://opensea.io/collection/pudgypenguins

You can provide multiple collections:

pudgypenguins
azuki
doodles-official

Each collection is processed independently.

---

🔢 Maximum NFT Items

Set the total maximum number of NFTs to return per collection.

Minimum: 1
Default: 20
Maximum: 1000

Example:

Collection:
pudgypenguins

Maximum NFT Items:
250

can return up to:

250 Dataset rows

The requested number is a maximum, not a guarantee. If OpenSea returns fewer available NFT items, the Actor stops naturally instead of generating fake records.

---

🧪 Example input

{
  "collectionReferences": [
    "pudgypenguins"
  ],
  "maxItems": 250
}

Multiple collections:

{
  "collectionReferences": [
    "https://opensea.io/collection/pudgypenguins",
    "https://opensea.io/collection/azuki"
  ],
  "maxItems": 100
}

With two collections and maxItems: 100, the Actor can return up to:

100 NFTs from collection 1
+
100 NFTs from collection 2
=
200 Dataset rows

---

⬆️ Output

Results are stored in the Actor's default Apify Dataset.

You can access results from:

Output
Storage
Apify API
Integrations
Export

Each successful Dataset row represents one NFT.

This structure works well for:

JSON
CSV
Excel
Databases
Data warehouses
Google Sheets
Make
Zapier
AI workflows
Custom applications

---

📊 Example result

{
  "collectionReference": "pudgypenguins",
  "slug": "pudgypenguins",
  "collectionName": "Pudgy Penguins",
  "collectionUrl": "https://opensea.io/collection/pudgypenguins",
  "collectionImageUrl": "https://i2c.seadn.io/collection/...",
  "category": "pfps",
  "floorPrice": 3.80399999,
  "floorCurrency": "ETH",
  "totalVolume": 520657.3285229603,
  "volumeCurrency": "ETH",
  "totalSales": 92084,
  "owners": 5085,
  "tokenId": "8887",
  "nftName": "Pudgy Penguin #8887",
  "nftDescription": "A collection 8888 Cute Chubby Pudgy Penquins sliding around on the freezing ETH blockchain.",
  "nftUrl": "https://opensea.io/assets/ethereum/0xbd3531da5cf5857e7cfaa92426877b022e612cf8/8887",
  "nftImageUrl": "https://i2c.seadn.io/ethereum/...",
  "contract": "0xbd3531da5cf5857e7cfaa92426877b022e612cf8",
  "tokenStandard": "erc721",
  "metadataUrl": "https://opensea-private.mypinata.cloud/ipfs/...",
  "animationUrl": null,
  "traits": [
    {
      "trait_type": "Body",
      "display_type": null,
      "max_value": null,
      "value": "Puffer Green"
    },
    {
      "trait_type": "Background",
      "display_type": null,
      "max_value": null,
      "value": "Blue"
    }
  ],
  "traitsText": "Body: Puffer Green, Background: Blue",
  "estimatedValueUsd": null,
  "isNsfw": false,
  "isDisabled": false,
  "nftUpdatedAt": "2026-09-07T06:33:29.473903",
  "hasNextPage": true,
  "nextCursor": "WyIyMDIxLTA3LTIyVDIwOjE4OjE0WiIs...",
  "observedAt": "2026-09-07T06:33:29.865Z"
}

---

🧬 NFT traits

The Actor returns NFT traits in two formats.

Structured traits

[
  {
    "trait_type": "Body",
    "value": "Puffer Green"
  },
  {
    "trait_type": "Background",
    "value": "Blue"
  }
]

Useful for:

Databases
JSON APIs
Trait filtering
Rarity research
Data science
Custom applications

Traits text

The same traits are also returned in:

traitsText

Example:

Body: Puffer Green, Face: Handlebar Bear, Head: Flat Cap Tan, Skin: Olive Green, Background: Blue

Useful for:

CSV
Excel
Google Sheets
Simple automation workflows

---

📊 Collection statistics

Each NFT row includes collection-level statistics observed during the same run:

floorPrice
floorCurrency
totalVolume
volumeCurrency
totalSales
owners

These values are repeated on every NFT row intentionally so exported data remains self-contained.

Collection statistics can change over time. They represent the values observed during that Actor run.

---

📄 Pagination

OpenSea NFT Scraper automatically handles cursor-based pagination.

The Actor continues until:

• 🎯 the requested maxItems total is reached
• 📭 OpenSea returns no additional NFT items
• ⛔ OpenSea stops returning a next cursor
• ⚠️ a request fails
• 🛡 the current 1,000-NFT-per-collection Actor limit is reached

Example:

Requested total: 250 NFTs

The Actor can fetch multiple API pages and combine them into:

250 NFT Dataset rows

You do not need to manually provide or manage OpenSea pagination cursors.

---

➡️ hasNextPage and nextCursor

Every returned NFT row includes:

hasNextPage
nextCursor

These describe whether OpenSea indicated that more NFT results remained after the final page fetched for the requested batch.

Example:

{
  "hasNextPage": true,
  "nextCursor": "WyIyMDIxLTA3LTIyVDIwOjE4OjE0WiIs..."
}

---

🔍 Multiple collections

Example:

{
  "collectionReferences": [
    "pudgypenguins",
    "azuki",
    "doodles-official"
  ],
  "maxItems": 100
}

Each collection is processed independently.

Every NFT row preserves:

collectionReference
slug
collectionName
collectionUrl

so downstream systems can identify the source collection.

---

🧹 Dataset structure

The Actor uses:

1 NFT = 1 Dataset row

So:

250 NFTs

returns up to:

250 Dataset rows

instead of putting hundreds of NFTs inside one nested Dataset item.

This makes results easier to:

Filter
Sort
Export
Search
Analyze
Store
Transform
Automate

---

⚡ Performance

OpenSea NFT Scraper uses an HTTP/API-first architecture.

It communicates with OpenSea data endpoints without launching browser automation for the normal collection workflow.

Benefits include:

Fast startup
Low browser overhead
Lower memory requirements
Structured API responses
Efficient pagination
Clean Dataset output

A verified Actor test requested 250 Pudgy Penguins NFT items and returned 250 separate Dataset rows.

Actual runtime can vary depending on the requested NFT count, number of collections, OpenSea response time, and Apify platform conditions.

---

🛡 Reliability

Each collection is processed independently.

If one collection fails, successful results from other collections can remain in the Dataset.

Failed collection rows include available context such as:

collectionReference
slug
observedAt
error

Invalid OpenSea collection URLs are handled without fabricating data.

---

🔌 API & integrations

OpenSea NFT Scraper can be used programmatically through the Apify API.

Connect results to workflows such as:

• Google Sheets
• Make
• Zapier
• Airtable
• Databases
• Data warehouses
• Internal APIs
• NFT analytics tools
• Research pipelines
• AI agents
• MCP workflows
• Custom dashboards

Every Actor run stores structured NFT results in the default Apify Dataset.

---

💡 Example use cases

📊 NFT collection research

Analyze:

Floor price
Collection volume
Total sales
Owner count
NFT names
Token IDs
Traits
Images
Contracts

---

🧬 Trait analysis

Use the raw traits array or traitsText to study:

Trait frequency
Trait combinations
Background distribution
Body types
Head traits
Skin traits
Other collection-specific attributes

---

📈 Collection monitoring

Run the Actor at different times and compare:

Floor price
Total volume
Sales
Owner count
NFT metadata changes

Use observedAt to identify when the dataset was collected.

---

🗃 NFT dataset building

Build datasets for:

Machine learning
Research
Analytics
Search systems
Recommendation systems
Data enrichment
NFT dashboards
Internal databases

---

⚙️ Automation workflows

Send one-NFT-per-row data to:

Make
Zapier
Google Sheets
Data warehouses
Internal services
Custom APIs
AI systems

---

⚠️ Current limitations

The current version focuses on collection NFT extraction and normalized NFT metadata.

It does not currently provide dedicated modes for:

Wallet portfolio scraping
Wallet activity history
Individual account profiles
NFT ownership history
Full sale-event history
Bid history
Offer history
Listing history
Marketplace order execution
NFT buying or selling
Trait rarity scoring
Cross-marketplace price comparison
Historical floor-price charts
Automatic image downloading
More than 1,000 NFTs per collection in one run

The current Actor is intentionally focused on reliable collection NFT data rather than combining every OpenSea feature into one workflow.

---

❓ FAQ

How does OpenSea NFT Scraper work?

The Actor:

Accepts collection URLs or slugs
Resolves the collection slug
Fetches collection information
Fetches collection statistics
Fetches NFT items
Follows pagination cursors when needed
Normalizes NFT metadata
Creates one Dataset row per NFT
Stores results in Apify Dataset

---

How many NFTs can I scrape?

Current input range:

Minimum: 1 per collection
Default: 20 per collection
Maximum: 1000 per collection

The requested value is a maximum. If fewer NFT items are available, the Actor returns fewer rows.

---

Can I scrape more than 200 NFTs?

Yes.

Pagination is automatic.

For example:

{
  "collectionReferences": ["pudgypenguins"],
  "maxItems": 250
}

can return:

250 Dataset rows

without manually providing a cursor.

---

Can I scrape multiple collections in one run?

Yes.

Example:

{
  "collectionReferences": [
    "pudgypenguins",
    "azuki"
  ],
  "maxItems": 100
}

---

Can I use full OpenSea collection URLs?

Yes.

Supported:

pudgypenguins

and:

https://opensea.io/collection/pudgypenguins

---

Why are some fields null?

OpenSea does not expose every field for every NFT.

For example:

animationUrl
estimatedValueUsd
metadataUrl

can be unavailable.

The Actor returns null instead of inventing missing values.

---

Why is collection data repeated on every NFT row?

This is intentional.

Fields such as:

collectionName
floorPrice
totalVolume
totalSales
owners

are repeated so each exported NFT row is self-contained.

---

What does traitsText contain?

It converts structured NFT traits into readable text.

Example:

Body: Puffer Green, Face: Handlebar Bear, Head: Flat Cap Tan, Skin: Olive Green, Background: Blue

The raw traits array is still included.

---

What does hasNextPage mean?

hasNextPage: true means OpenSea indicated that more results remained beyond the final batch fetched in the current run.

The corresponding cursor is stored in:

nextCursor

---

Can I export the results?

Yes.

Apify Dataset supports exports such as:

JSON
CSV
Excel
XML
HTML

---

Can I use the scraper through an API?

Yes.

The Actor can be started through the Apify API, and its Dataset can be accessed programmatically.

---

Does the Actor use browser automation?

Not for the normal collection workflow.

The current Actor uses an HTTP/API-first approach.

---

Does it buy, sell, or transfer NFTs?

No.

This Actor is for data extraction and analysis only.

---

🧭 Recommended workflow

Start with a small test:

{
  "collectionReferences": [
    "pudgypenguins"
  ],
  "maxItems": 20
}

Verify the fields you need, then increase the amount:

{
  "collectionReferences": [
    "pudgypenguins"
  ],
  "maxItems": 250
}

Remember that maxItems is applied per collection.

Example:

3 collections
×
250 NFTs maximum each
=
up to 750 Dataset rows

---

💬 Feedback & support

Found a bug or have a feature request?

Use the Actor's Issues tab on Apify.

Potential future additions:

Wallet mode
Activity/event mode
Collection history
Listings
Offers
Sales history
Trait rarity analysis
More configurable output modes
Higher per-collection limits
Additional NFT marketplace intelligence

---

🚀 OpenSea NFT data without the manual searching

Enter one or more OpenSea collection URLs or slugs, choose how many NFT items you want, run the Actor, and receive structured OpenSea NFT data ready for research, analytics, APIs, automation, spreadsheets, and data pipelines.