So now let's say you've deployed your contract on the Rinkeby test network. For a concrete example, we deployed the OpenSea Creature contract on Rinkeby to the following address: 0x7dca125b1e805dc88814aed7ccc810f677d3e1db.
We also minted 25 new items to this contract, so that the total supply of items is currently 25. On Etherscan, we can inspect the
tokenURI for one of these items to see that it points to the OpenSea Creature API endpoint.
Now for the exciting part! OpenSea has a Rinkeby environment that allows developers to test their integration with OpenSea. This can be found at testnets.opensea.io. By hitting the right URL, we should be able to immediately view one of our items on OpenSea. The URL can be constructed in the following way:
asset_contract_address is the address of our contract, and
token_id is one of the token id's of our items. For example, for the OpenSea Creature contract, here's OpenSea Creature #12:
By using your own contract address and token ID, you can view your item too and double check that everything shows up as expected. Notice that the attributes we included in the token metadata showed up as "properties" and "stats" for the item. This will automatically happen as long as you include them as strings or ints in the attributes section of your metadata. To test out the integration, simply navigate to:
By default, OpenSea will cache the data for your asset. Need to force an update to your item? Just hit the API with the
If you're having issues getting your items to show up properly on OpenSea (perhaps they're missing an image or attributes), you can debug your metadata using the following API endpoint.
Check out the next section for info on debugging.
If your metadata is showing up as expected, you can skip straight to section 5.
Updated about 1 year ago