How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OpenSea Collection Endpoints API

Collection endpoints to retrieve collection details, traits, and trending data

OpenSea Collection Endpoints API is one of 17 APIs that OpenSea publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Collection Endpoints. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 11 paths, and defines 22 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.

Requests are made against a single base URL, https://api.opensea.io.

11 operations 11 paths 22 schemas 10 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Base URL
https://api.opensea.io/api/v2
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

OpenSea Collection Endpoints API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key required for authentication

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 10 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Collection Endpoints 11

Collection endpoints to retrieve collection details, traits, and trending data

POST
/api/v2/collections/batch
Get collections by slugs
get_collections_batch body → 200400500
GET
/api/v2/traits/{slug}
Get collection traits
get_collection_traits 1 param → 200400404500
GET
/api/v2/collections
Get multiple collections
list_collections 6 params → 200400404500
GET
/api/v2/collections/{slug}
Get a single collection
get_collection 1 param → 200400404500
GET
/api/v2/collections/{slug}/stats
Get collection stats
get_collection_stats 1 param → 200400404500
GET
/api/v2/collections/{slug}/offer_aggregates
Get collection offer aggregates
get_collection_offer_aggregates 4 params → 200400500
GET
/api/v2/collections/{slug}/holders
Get collection holders
get_collection_holders 5 params → 200400500
GET
/api/v2/collections/{slug}/floor_prices
Get collection floor price history
get_collection_floor_prices 3 params → 200400500
GET
/api/v2/collections/trending
Get trending collections
get_trending_collections 5 params → 200400500
GET
/api/v2/collections/top
Get top collections
get_top_collections 5 params → 200400500
GET
/api/v2/chain/{chain}/contract/{address}/nfts/{identifier}/collection
Get collection by NFT
get_nft_collection 3 params → 200400404500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are CollectionDetailedResponse (28 properties), CollectionResponse (20 properties), PaymentToken (8 properties), Total (5 properties). Each schema is shown below with its type and property counts.

CollectionBatchResponse
object
1 property 1 required
CollectionStatsResponse
object
2 properties 2 required
CollectionDetailedResponse
object
28 properties 15 required
PricingCurrencies
object
2 properties 2 required
CollectionHoldersPaginatedResponse
object
Paginated list of collection holders
2 properties 1 required
BatchCollectionsRequest
object
Request body for batch collection retrieval by slugs
1 property 1 required
FloorPriceHistoryResponse
object
Floor price history for a collection
1 property 1 required
Contract
object
2 properties 2 required
PaymentToken
object
8 properties 8 required
BidderResponse
object
A bidder in an offer aggregate
2 properties 2 required
CollectionPaginatedResponse
object
2 properties 1 required
ChainIdentifier
string
Blockchain chain identifier. Use the chain slug (e.g., 'ethereum', 'polygon', 'arbitrum', 'optimism', 'base')
CollectionResponse
object
20 properties 9 required
CollectionHolderResponse
object
A collection holder
3 properties 3 required
CollectionOfferAggregatesPaginatedResponse
object
Paginated list of collection offer aggregates
2 properties 1 required
CollectionOfferAggregateResponse
object
An aggregated offer bucket
4 properties 4 required
IntervalStat
object
3 properties 3 required
CollectionRarity
object
5 properties 5 required
FloorPricePointResponse
object
A floor price data point
5 properties 1 required
Total
object
5 properties 5 required
Fee
object
3 properties 3 required
OfferAggregatePriceResponse
object
Price information for an offer aggregate
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opensea-collection-endpoints-api-openapi.yml Raw ↑

Other APIs OpenSea publishes across the network.

OpenSea Stream API
OpenSea Account Endpoints API
OpenSea Analytics Endpoints API
OpenSea Auth Endpoints API
OpenSea Chain Endpoints API
OpenSea Contract Endpoints API
OpenSea Drops Endpoints API
OpenSea Listing Endpoints API
OpenSea NFT Endpoints API
OpenSea Offer Endpoints API
OpenSea Order Endpoints API
OpenSea Search Endpoints API
Where this information came from

This is an independent, third-party profile of OpenSea Collection Endpoints API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.