Error when trying to add nft (/nft url)

Developer help
1

I get these errors from trying to add any OpenSea NFT from my profile to a post from this menu:
image

Example NFT url:

image
image768×74 2.59 KB

Get errors:

image
image971×90 10 KB

Any idea how I can get this working?

2

OpenSea are currently blocking embeds - no idea why - there’s nothing we can do about it unfortunately, it’s something that OpenSea would need to change in order to start working again

3

Hmmm that’s weird cause you can click on:
image

And it will show up as an embed like this:

image
image715×256 38.5 KB

Looking at the code:


    <nft-card
    contractAddress="0x495f947276749ce646f68ac8c248420045cb7b5e"
    tokenId="103033592749126324964984029375526861196619007344243593146064831559815271546881">
    </nft-card>
    <script src="https://unpkg.com/embeddable-nfts/dist/nft-card.min.js"></script>

The contractAddress and tokenId are the only variables needed in order to create this embed.
If you look closely at the OpenSea link I provided, both are included in the url.

So this must be a mistake somewhere right?
If you could point me out where this file is creating this function, I could manually modify it though with an easy script

4

Has this been solved somehow? @John

Seems like OS isn’t blocking Embeds right now at least, but I’m still getting the error.

5

Still not working for me at least.

6

Would like to have a solution to this as well. Try to work something out on my end.

7

I am having the same issues, and I am hacking on it.
I absolutely can not get the OpenSea integration to work for some reason.

When I use the HTML embed integration, I can only get it to work for NFTs minted on ETH… not the free Polygon minted NFTs.
After being sent to GitHub from the OpenSea Docs I see there is an option for Network

<nft-card
  tokenAddress="0x5caebd3b32e210e85ce3e9d51638b9c445481567"
  tokenId="2242579050293992223"
  **network="mainnet"**
  >
</nft-card>

I am working on trying to get those to even show up at all…
When I do, I will share.

Might also have to create a new integration.
The current one will not take a link to any ETH or Poly NFT.

I am pretty sure It is not OpenSea blocking.