it looks like it uses an oder version of Moralis SDK, 0.0.104, you could try with 0.0.184, also you could paste as text that payload
How can I do that? Can you explain me?
{network: "mainnet", tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb", tokenId: "926",…}
endAmount: 0.5
expirationTime: 1642716466
network: "mainnet"
startAmount: 1
tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb"
tokenId: "926"
tokenType: "ERC721"
userAddress: "0xc092d93795ed6610ecfa9d454d534af3e029375b"
_ApplicationId: "wYSxHFNeSKgj9hUDnBCQJ5dg5XR0xZpIsFG0Vl2w"
_ClientVersion: "js0.0.104"
_InstallationId: "96ca8672-4b18-4c6c-9209-e8805e92210b"
_SessionToken: "r:cb5a1d0c177a0ed8725b28a08751bb11"
{network: "mainnet", tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb", tokenId: "926",…}
network: "mainnet"
tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb"
tokenId: "926"
_ApplicationId: "wYSxHFNeSKgj9hUDnBCQJ5dg5XR0xZpIsFG0Vl2w"
_ClientVersion: "js0.0.104"
_InstallationId: "96ca8672-4b18-4c6c-9209-e8805e92210b"
_SessionToken: "r:cb5a1d0c177a0ed8725b28a08751bb11"
usually there is a line like this that you add in your html file:
<script src="https://unpkg.com/[email protected]/dist/moralis.js"></script>
you can also try to update opensea plugin in case that it is not the latest version
How can I do that with .js file? Sorry for this question. I am not programmer. I tried to find solution in google, but I did’t understand how do that.
Thank you for your reply.
I ran the command you wrote. But the error did not disappear, but a message appeared stating (yellow) that I am not using the latest version of the SDK.
I repeated the command with a recommended version number:
yarn add [email protected]
After that, all yellow messages disappeared.
But with the buttons, the red errors remained.
Create Sell Order
Playload
{network: "mainnet", tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb", tokenId: "926",…}
endAmount: 0.5
expirationTime: 1642748647
network: "mainnet"
startAmount: 1
tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb"
tokenId: "926"
tokenType: "ERC721"
userAddress: "0xc092d93795ed6610ecfa9d454d534af3e029375b"
_ApplicationId: "wYSxHFNeSKgj9hUDnBCQJ5dg5XR0xZpIsFG0Vl2w"
_ClientVersion: "js1.0.7"
_InstallationId: "96ca8672-4b18-4c6c-9209-e8805e92210b"
_SessionToken: "r:f3093fd0259dd590f5c82d8cf1fe15bc"
Get Asset and Get Order same error
Playload:
{network: "mainnet", tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb", tokenId: "926",…}
network: "mainnet"
tokenAddress: "0xA905736754e8Caf16020849b370bA056d372e6Cb"
tokenId: "926"
_ApplicationId: "wYSxHFNeSKgj9hUDnBCQJ5dg5XR0xZpIsFG0Vl2w"
_ClientVersion: "js1.0.7"
_InstallationId: "96ca8672-4b18-4c6c-9209-e8805e92210b"
_SessionToken: "r:f3093fd0259dd590f5c82d8cf1fe15bc"
I also checked the version of the OpenSea plugin.
In the admin panel, version 0.0.83. Same as on the plugin page: https://moralis.io/plugins/opensea/
it looks like I get same error, it seems to be a restriction from OpenSea
What can I do with this? How to fix it?
Hey @Den
This is not something you can fix yourself since the error comes directly from OpenSea.
We just contacted them asking to investigate.
Fingers crossed, let’s see what they say.
1 Like
Any news on this issue?
Hey Dani
Same issue here.
Is this possibly due to the API restrictions OS put in place just recently? There is a slot in the plugin config for OS API key, but it says optional. I suspect it’s not optional any more. The problem is of course that OS is pretty much not handing out API keys any more. To get a key you need to tell them what you want to do and link to your project. How can we link to a project if we haven’t built it yet? Catch 22 here.
I have same problem here when trying to access some resource by address which is posted in opensea…
This makes a lot of functionality in Moralis for NFTs broken now, doesn’t it? OS only giving out keys now if you can show a live project website or github, how we’re supposed to do that in development phase I don’t know.
Moralis NFT API works perfectly https://docs.moralis.io/moralis-server/web3-sdk/nft-api
Opensea plug-in is not moralis tech - it’s just a wrapper around their API so when they have issues the plug-in won’t work - moralis has no control over that
Good to know, thanks, we’ll switch to RnD on that one.
Can it do everything that OS’s native JS SDK can do? Find, buy, sell, bid, etc
Took a look at the NFT API but you can’t use it to buy and sell? So how do we do the OS marketplace clone when OS is no longer giving out API keys (unless you have an active, live project and discord history, impossible when starting out).
The OS plugin does one thing, the Moralis NFT API does something else entirely. The NFT API is not a replacement for the OS Plugin? Where do we go from here.
Right so this is an “alternative” to OS, not working “with” OS.
<ShoppingCartOutlined
onClick={() => alert("OPENSEA INTEGRATION COMING!")}
/>
Which is not great because if the floor goes up on OS, a custom and separate marketplace would be way out of sync with the actual market. How does it work if you list something for sale on the Boilerplate/fork market, and that item is also listed on OS and bought by someone? Is the offer on the boilerplate marketplace then invalid? Does it still show up and confuse people when they’re browsing to buy something?
Seems like it would be a good way to have a “single project” market on the project website - but not if there’s no OS or LooksRare integration and not if there are completely different buy/sell offers in each market.