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 Listing Endpoints API

Listing endpoints for creating, fulfilling, and querying listings

OpenSea Listing 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 Listing Endpoints. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 8 paths, and defines 51 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.

8 operations 8 paths 51 schemas 3 GET5 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 Listing 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 8

Across 8 paths, the API surfaces 8 operations — 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Listing Endpoints 8

Listing endpoints for creating, fulfilling, and querying listings

POST
/api/v2/orders/{chain}/{protocol}/listings
Create a listing
post_listing 2 params body → 200400500
POST
/api/v2/listings/sweep
Sweep buy items from a collection
sweep_collection body → 200400500
POST
/api/v2/listings/fulfillment_data
Fulfill a listing
generate_listing_fulfillment_data_v2 body → 200400500
POST
/api/v2/listings/cross_chain_fulfillment_data
Fulfill a listing using a different token
generate_cross_chain_listing_fulfillment_data body → 200400500
POST
/api/v2/listings/actions
Get listing creation actions
create_listing_actions body → 200400500
GET
/api/v2/listings/collection/{slug}/nfts/{identifier}/best
Get best listing by NFT
get_best_listing_nft 3 params → 200400404500
GET
/api/v2/listings/collection/{slug}/best
Get best listings by collection
get_best_listings_collection 5 params → 200400404500
GET
/api/v2/listings/collection/{slug}/all
Get all listings by collection
list_listings_collection_all 5 params → 200400404500

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are BasicOrderParameters (21 properties), OrderParameters (14 properties), Parameters (12 properties), SeaportParameters (12 properties). Each schema is shown below with its type and property counts.

FulfillerObject
object
1 property 1 required
CreateListingActionsRequest
object
Request to get listing creation actions
4 properties 2 required
SweepCollectionRequest
object
Request to sweep buy items from a collection
6 properties 5 required
SweepCollectionResponse
object
Response containing ordered blockchain actions to execute for a collection sweep
2 properties 1 required
ListingPrice
object
1 property 1 required
Address
object
2 properties
ListingObject
object
3 properties 3 required
MatchAdvancedOrders
4 required
FullfillListingRequest
object
6 properties 2 required
AdvancedOrder
object
8 properties
MatchOrders
2 required
SeaportCall
Fulfillment
object
5 properties
Parameters
object
12 properties 12 required
Uint256
object
3 properties
AdditionalRecipient
object
5 properties
FulfillmentComponent
object
5 properties
BasicOrderParameters
object
21 properties
Item
object
5 properties 5 required
ListingOrOffer
OrderAsset
object
2 properties 1 required
CriteriaResolver
object
8 properties
CreateListingActionsResponse
object
Response containing blockchain actions to execute for listing creation
1 property 1 required
FulfillListingResponse
object
2 properties 2 required
FulfillmentData
object
2 properties 2 required
Price
object
3 properties 3 required
OfferItem
object
5 properties 5 required
CrossChainFulfillmentRequest
object
Request to fulfill one or more listings using a payment token on a different chain or a different token on the same chain
4 properties 3 required
TransactionData
object
5 properties 5 required
FulfillAvailableAdvancedOrders
7 required
CrossChainFulfillmentResponse
object
Response containing ordered transactions to execute for cross-chain fulfillment
1 property 1 required
SwapTransactionResponse
object
A transaction to be submitted onchain to execute a swap
4 properties 2 required
ListingsResponse
object
2 properties 1 required
FulfillBasicOrder
1 required
SeaportRequest
object
3 properties 3 required
FulfillAdvancedOrder
4 required
JsonNode
Order
object
7 properties 3 required
ConsiderationItem
object
6 properties 6 required
ProtocolData
object
2 properties 1 required
Type
object
2 properties
OrderParameters
object
14 properties
SweepError
object
An error encountered during a sweep operation
1 property 1 required
ListingItem
object
An item to list for sale
7 properties 5 required
CrossChainPaymentToken
object
Payment token to use for cross-chain fulfillment
2 properties 2 required
SeaportParameters
object
12 properties 11 required
OrderData
object
2 properties 2 required
FulfillAvailableOrders
5 required
FulfillOrder
2 required
Listing
6 required
ConsiderationObject
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opensea-listing-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 Collection Endpoints API
OpenSea Contract Endpoints API
OpenSea Drops 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 Listing 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.