A JavaScript library for crypto-native e-commerce: buying, selling, and bidding on NFTs (non-fungible tokens). With OpenSea.js, you can easily build your own native marketplace. These can be ERC-721 or ERC-1155 (semi-fungible) items. You don't have to deploy your own smart contracts or manage backend orderbooks.
- Synopsis
- Installation
- Getting Started
- Advanced
- Learning More
- Changelog
- Development Information
- Diagnosing Common Issues
- Testing your branch locally
This is the JavaScript SDK for OpenSea, the largest marketplace for NFTs.
It allows developers to access the official orderbook, filter it, create buy orders (offers), create sell orders (listings), and complete trades programmatically.
Get started by requesting an API key and instantiating your own OpenSea SDK instance. Then you can create orders off-chain or fulfill orders on-chain, and listen to events (like ApproveAllAssets or WrapEth) in the process.
Happy seafaring! ⛵️
Node.js version 16 is the minimum required for the SDK. Execute nvm use, if you have Node Version Manager.
Then, in your project, run:
npm install --save opensea-js
# or
yarn add opensea-jsTo get started, first request an API key. Note the terms of use for using API data.
Then, create a new OpenSeaJS client, called an OpenSeaSDK 🚢, using your web3 provider:
import { ethers } from "ethers";
import { OpenSeaSDK, Chain } from "opensea-js";
// This example provider won't let you make transactions, only read-only calls:
const provider = new ethers.providers.JsonRpcProvider(
"https://mainnet.infura.io",
);
const openseaSDK = new OpenSeaSDK(provider, {
chain: Chain.Mainnet,
apiKey: YOUR_API_KEY,
});NOTE: For testnet, please use Chain.Goerli as the chain. Rinkeby was deprecated in 2022.
NOTE: Using the sample provider above won't let you authorize transactions, which are needed when approving and trading assets and currency. To make transactions, you need a provider with a private key or mnemonic set.
In a browser with web3 or an extension like MetaMask or Coinbase Wallet, you can use window.ethereum to access the native provider.
Assets are items on OpenSea. They can be non-fungible (conforming to standards like ERC721), semi-fungible (like ERC1155 assets), and even fungible (ERC20).
Assets are represented by the Asset type, defined in TypeScript:
/**
* Simple, unannotated non-fungible asset spec
*/
export interface Asset {
// The asset's token ID, or null if ERC-20
tokenId: string | null,
// The asset's contract address
tokenAddress: string,
// The schema name (defaults to "ERC721") for this asset
tokenStandard?: TokenStandard,
// Optional for ENS names
name?: string,
// Optional for fungible items
decimals?: number
}The Asset type is the minimal type you need for most marketplace actions. TokenStandard is optional. If omitted, most actions will assume you're referring to a non-fungible, ERC721 asset. Other options include 'ERC20' and 'ERC1155'. You can import import { TokenStandard } from "opensea-js/lib/types" to get the full range of schemas supported.
You can fetch an asset using the OpenSeaAPI, which will return an OpenSeaAsset for you (OpenSeaAsset extends Asset):
const asset: OpenSeaAsset = await openseaSDK.api.getAsset({
tokenAddress, // string
tokenId, // string | number | BigNumber | null
})Note that fungible ERC20 assets have null as their token id.
The nice thing about the Asset type is that it unifies logic between fungibles, non-fungibles, and semi-fungibles.
Once you have an Asset, you can see how many any account owns, regardless of whether it's an ERC-20 token or a non-fungible good:
const asset = {
tokenAddress: "0x06012c8cf97bead5deae237070f9587f8e7a266d", // CryptoKitties
tokenId: "1", // Token ID
};
const balance = await openseaSDK.getBalance({
accountAddress, // string
asset, // Asset
});
const ownsKitty = balance.greaterThan(0);Once you have your asset, you can do this to make an offer on it:
// Token ID and smart contract address for a non-fungible token:
const { tokenId, tokenAddress } = YOUR_ASSET;
// The offerer's wallet address:
const accountAddress = "0x1234...";
const offer = await openseaSDK.createBuyOrder({
asset: {
tokenId,
tokenAddress,
tokenStandard, // TokenStandard. If omitted, defaults to 'ERC721'. Other options include 'ERC20' and 'ERC1155'
},
accountAddress,
// Value of the offer, in units of the payment token (or wrapped ETH if none is specified):
startAmount: 1.2,
});When you make an offer on an item owned by an OpenSea user, that user will automatically get an email notifying them with the offer amount, if it's above their desired threshold.
Note: The total value of buy orders must not exceed 1000 x wallet balance.
To sell an asset, call createSellOrder. You can do a fixed-price listing, where startAmount is equal to endAmount, or a declining Dutch auction, where endAmount is lower and the price declines until expirationTime is hit:
// Expire this auction one day from now.
// Note that we convert from the JavaScript timestamp (milliseconds):
const expirationTime = Math.round(Date.now() / 1000 + 60 * 60 * 24);
const listing = await openseaSDK.createSellOrder({
asset: {
tokenId,
tokenAddress,
},
accountAddress,
startAmount: 3,
// If `endAmount` is specified, the order will decline in value to that amount until `expirationTime`. Otherwise, it's a fixed-price order:
endAmount: 0.1,
expirationTime,
});The units for startAmount and endAmount are Ether, ETH. If you want to specify another ERC-20 token to use, see Using ERC-20 Tokens Instead of Ether.
See Listening to Events to respond to the setup transactions that occur the first time a user sells an item.
English Auctions are auctions that start at a small amount (we recommend even doing 0!) and increase with every bid. At expiration time, the item sells to the highest bidder.
To create an English Auction, create a listing that waits for the highest bid by setting waitForHighestBid to true:
// Create an auction to receive Wrapped Ether (WETH). See note below.
const paymentTokenAddress = "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2";
const startAmount = 0; // The minimum amount to sell for, in normal units (e.g. ETH)
const order = await openseaSDK.createSellOrder({
asset: {
tokenId,
tokenAddress,
},
accountAddress,
startAmount,
expirationTime,
paymentTokenAddress,
waitForHighestBid: true,
});Note that auctions aren't supported with Ether directly due to limitations in Ethereum, so you have to use an ERC20 token, like Wrapped Ether (WETH), a stablecoin like DAI, etc. See Using ERC-20 Tokens Instead of Ether for more info.
To retrieve a list of offers and auctions on an asset, you can use an instance of the OpenSeaAPI exposed on the client. Parameters passed into API filter objects are camel-cased and serialized before being sent as OpenSea API parameters:
// Get offers (bids), a.k.a. orders where `side == 0`
const { orders, count } = await openseaSDK.api.getOrders({
assetContractAddress: tokenAddress,
tokenId,
side: "bid",
});
// Get page 2 of all auctions, a.k.a. orders where `side == 1`
const { orders, count } = await openseaSDK.api.getOrders(
{
assetContractAddress: tokenAddress,
tokenId,
side: "ask",
},
2,
);Note that the listing price of an asset is equal to the currentPrice of the lowest valid sell order on the asset. Users can lower their listing price without invalidating previous sell orders, so all get shipped down until they're canceled, or one is fulfilled.
To learn more about signatures, makers, takers, listingTime vs createdTime and other kinds of order terminology, please read the Terminology Section of the API Docs.
The available API filters for the orders endpoint is documented in the OrdersQueryOptions interface below, but see the main API Docs for a playground, along with more up-to-date and detailed explanations.
/**
* Attrs used by orderbook to make queries easier
* More to come soon!
*/
side: "bid" | "ask", // "bid" for buy orders, "ask" for sell orders
protocol?: "seaport"; // Protocol of the order (more options may be added in future)
maker?: string, // Address of the order's creator
taker?: string, // The null address if anyone is allowed to take the order
owner?: string, // Address of owner of the order's item
sale_kind?: SaleKind, // 0 for fixed-price, 1 for Dutch auctions
assetContractAddress?: string, // Contract address for order's item
paymentTokenAddress?: string; // Contract address for order's payment token
tokenId?: number | string,
tokenIds?: Array<number | string>,
listedAfter?: number | string, // This means listing_time > value in seconds
listedBefore?: number | string, // This means listing_time <= value in seconds
orderBy?: "created_date" | "eth_price", // Field to sort results by
orderDirection?: "asc" | "desc", // Sort direction of orderBy sorting of results
onlyEnglish?: boolean, // Only return english auction orders
// For pagination
limit?: number,
offset?: number,To buy an item, you need to fulfill a sell order. To do that, it's just one call:
const order = await openseaSDK.api.getOrder({ side: "ask", ... })
const accountAddress = "0x..." // The buyer's wallet address, also the taker
const transactionHash = await openseaSDK.fulfillOrder({ order, accountAddress })Note that the fulfillOrder promise resolves when the transaction has been confirmed and mined to the blockchain. To get the transaction hash before this happens, add an event listener (see Listening to Events) for the TransactionCreated event.
If the order is a sell order (order.side === "ask"), the taker is the buyer and this will prompt the buyer to pay for the item(s).
Similar to fulfilling sell orders above, you need to fulfill a buy order on an item you own to receive the tokens in the offer.
const order = await openseaSDK.api.getOrder({ side: "bid", ... })
const accountAddress = "0x..." // The owner's wallet address, also the taker
await openseaSDK.fulfillOrder({ order, accountAddress })If the order is a buy order (order.side === "bid"), then the taker is the owner and this will prompt the owner to exchange their item(s) for whatever is being offered in return. See Listening to Events below to respond to the setup transactions that occur the first time a user accepts a bid.
Interested in purchasing for users server-side or with a bot, scheduling future orders, or making bids in different ERC-20 tokens? OpenSea.js can help with that.
You can create sell orders that aren't fulfillable until a future date. Just pass in a listingTime (a UTC timestamp in seconds) to your SDK instance:
const order = await openseaSDK.createSellOrder({
tokenAddress,
tokenId,
accountAddress,
startAmount: 1,
listingTime: Math.round(Date.now() / 1000 + 60 * 60 * 24), // One day from now
});You can buy and transfer an item to someone else in one step! Just pass the recipientAddress parameter:
const order = await openseaSDK.api.getOrder({ side: "ask", ... })
await openseaSDK.fulfillOrder({
order,
accountAddress, // The address of your wallet, which will sign the transaction
recipientAddress // The address of the recipient, i.e. the wallet you're purchasing on behalf of
})If the order is a sell order (order.side === "ask"), the taker is the buyer and this will prompt the buyer to pay for the item(s) but send them to the recipientAddress. If the order is a buy order ( "bid"), the taker is the seller but the bid amount be sent to the recipientAddress.
This will automatically approve the assets for trading and confirm the transaction for sending them.
Here's an example of listing the Genesis CryptoKitty for $100! No more needing to worry about the exchange rate:
// Token address for the DAI stablecoin, which is pegged to $1 USD
const paymentTokenAddress = "0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359";
// The units for `startAmount` and `endAmount` are now in DAI, so $100 USD
const auction = await openseaSDK.createSellOrder({
tokenAddress: "0x06012c8cf97bead5deae237070f9587f8e7a266d", // CryptoKitties
tokenId: "1", // Token ID
accountAddress: OWNERS_WALLET_ADDRESS,
startAmount: 100,
paymentTokenAddress,
});You can use getPaymentTokens to search for tokens by symbol name. And you can even list all orders for a specific ERC-20 token by querying the API:
const token = (await openseaSDK.api.getPaymentTokens({ symbol: "MANA" }))
.tokens[0];
const order = await openseaSDK.api.getOrders({
side: "ask",
paymentTokenAddress: token.address,
});You can make offers and listings that can only be fulfilled by an address or email of your choosing. This allows you to negotiate a price in some channel and sell for your chosen price on OpenSea, without having to trust that the counterparty will abide by your terms!
Here's an example of listing a Decentraland parcel for 10 ETH with a specific buyer address allowed to take it. No more needing to worry about whether they'll give you enough back!
// Address allowed to buy from you
const buyerAddress = "0x123...";
const listing = await openseaSDK.createSellOrder({
tokenAddress: "0xf87e31492faf9a91b02ee0deaad50d51d56d5d4d", // Decentraland
tokenId:
"115792089237316195423570985008687907832853042650384256231655107562007036952461", // Token ID
accountAddress: OWNERS_WALLET_ADDRESS,
startAmount: 10,
buyerAddress,
});Events are fired whenever transactions or orders are being created, and when transactions return receipts from recently mined blocks on the Ethereum blockchain.
Our recommendation is that you "forward" OpenSea events to your own store or state management system. Here are examples of listening to the events:
import { openSeaSDK, EventType } from 'opensea-js'
handleSDKEvents() {
openSeaSDK.addListener(EventType.TransactionCreated, ({ transactionHash, event }) => {
console.info('Transaction created: ', { transactionHash, event })
})
openSeaSDK.addListener(EventType.TransactionConfirmed, ({ transactionHash, event }) => {
console.info('Transaction confirmed: ',{ transactionHash, event })
})
openSeaSDK.addListener(EventType.TransactionDenied, ({ transactionHash, event }) => {
console.info('Transaction denied: ',{ transactionHash, event })
})
openSeaSDK.addListener(EventType.TransactionFailed, ({ transactionHash, event }) => {
console.info('Transaction failed: ',{ transactionHash, event })
})
openSeaSDK.addListener(EventType.WrapEth, ({ accountAddress, amount }) => {
console.info('Wrap ETH: ',{ accountAddress, amount })
})
openSeaSDK.addListener(EventType.UnwrapWeth, ({ accountAddress, amount }) => {
console.info('Unwrap ETH: ',{ accountAddress, amount })
})
openSeaSDK.addListener(EventType.MatchOrders, ({ buy, sell, accountAddress }) => {
console.info('Match orders: ', { buy, sell, accountAddress })
})
openSeaSDK.addListener(EventType.CancelOrder, ({ order, accountAddress }) => {
console.info('Cancel order: ', { order, accountAddress })
})
}To remove all listeners call openseaSDK.removeAllListeners().
Auto-generated documentation for each export is available here.
See the Changelog.
Setup
Before any development, install the required NPM dependencies:
npm installAnd install TypeScript if you haven't already:
npm install -g typescriptBuild
Then, lint and build the library into the lib directory:
npm run buildOr run the tests:
npm testNote that the tests require access to Alchemy and the OpenSea API. The timeout is adjustable via the test script in package.json.
Generate Documentation
Generate html docs, also available for browsing here:
npm run docs-buildContributing
Contributions welcome! Please use GitHub issues for suggestions/concerns - if you prefer to express your intentions in code, feel free to submit a pull request.
-
Is the
expirationTimein the future? If not, change it to a time in the future. -
Are the input addresses all strings? If not, convert them to strings.
-
Is your computer's internal clock accurate? If not, try enabling automatic clock adjustment locally or following this tutorial to update an Amazon EC2 instance.
npm link # in opensea-js repo
npm link opensea-js # in repo you're working on