No metadata found for some NFTs

Technical Issue Reporting
#1

Iā€™ve been integrating the moralis APIā€™s into a project but ran into a snag where it couldnā€™t return the metadata. Iā€™m using the /nft/{address}/{id} endpoint like this

https://deep-index.moralis.io/api/v2/nft/0xcdFea41c4A8e70Fb4838426069483dC50cbf5041/3926?chain=matic&format=decimal

With this I get a correct response for every id until 671 which gives the response ā€œNo metadata found! Try again laterā€. Meanwhile there are NFTā€™s out there which have a much higher ID (like this one).

Is this a limitation of the API? Or is there something else Iā€™m missing?

#2

Try resyncing the metadata for it if you get that particular response or error - is the metadata field for 671 empty in the response? Web3API.token - Moralis

Otherwise fetch the token_uri and get the metadata manually.

#3

When trying I get the response below, Iā€™ll have a look into resyncing.

{
ā€œmessageā€: ā€œNo metadata found! Try again laterā€
}

#4

did you try to resync the uri or only the metadata?

you can try to resync the uri first, then check if that uri works/is available.

#5

Iā€™ve attempted resyncing the metadata using the APIs below. Iā€™ve also used the

https://deep-index.moralis.io/api/v2/nft/{address}/{id}/metadata/resync?chain=matic&flag=metadata&mode=async
https://deep-index.moralis.io/api/v2/nft/{address}/sync?chain=matic

Both return a success code so the requests whent through. After this the original requests still returns the same reply.

Which API is used to fetch the token URI?

#6

you can go to this page: https://admin.moralis.io/web3Api

and select uri, and will result this: https://deep-index.moralis.io/api/v2/nft/1241241244/1312312/metadata/resync?chain=eth&flag=uri&mode=sync

1 Like
#7

Iā€™ve used https://deep-index.moralis.io/api/v2/nft/{address}/{id}/metadata/resync?chain=eth&flag=uri&mode=sync it gives the following message: { "status": "The metadata could not be updated! Try again later" }

#8

ok, what is the token uri for that nft?

#9

It looks like this:

{
    "name": "Encode Bronze Key",
    "description": "Encode Bronze Key\n\n** Disclaimer ** Before purchase please ensure you check what Comic Books this key has claimed, the tool to check this is available at https://encode.network",
    "image": "https://enc-cbg.mypinata.cloud/ipfs/QmQdJLmXseBonCJe7qEShLDKBknLVXrP7Hv95BVV85ci84",
    "level": "BRONZE_LEVEL",
    "animation_url": "https://enc-cbg.mypinata.cloud/ipfs/Qmaptgxi4gFAqHdaDX6dGj4NmyAiD3nc13uEDJm6PhZoqE"
}
#10

this looks lie metadata, what is the url that points to this metadata?

#11

The URL is https://enc-cbg.mypinata.cloud/ipfs/bafkreiajbpvdi4srxjszzyu24gtbb3yr4z2sbnbjqvukr3yxlvyfqgiyke which I got from the API https://deep-index.moralis.io/api/v2/nft/0xcdFea41c4A8e70Fb4838426069483dC50cbf5041/1?chain=matic which returns the meta data for the token. The whole response is below:

{
    "token_address": "0xcdfea41c4a8e70fb4838426069483dc50cbf5041",
    "token_id": "1",
    "block_number_minted": "22632938",
    "owner_of": "0x012b623a1d2f05e2da7e9256c6d7b045b4d474c6",
    "block_number": "22632938",
    "amount": "1",
    "contract_type": "ERC721",
    "name": "EncodeKeys",
    "symbol": "ENCK",
    "token_uri": "https://enc-cbg.mypinata.cloud/ipfs/bafkreiajbpvdi4srxjszzyu24gtbb3yr4z2sbnbjqvukr3yxlvyfqgiyke",
    "metadata": "{\"name\":\"Encode Bronze Key\",\"description\":\"Encode Bronze Key\\n\\n** Disclaimer ** Before purchase please ensure you check what Comic Books this key has claimed, the tool to check this is available at https://encode.network\",\"image\":\"https://enc-cbg.mypinata.cloud/ipfs/QmQdJLmXseBonCJe7qEShLDKBknLVXrP7Hv95BVV85ci84\",\"level\":\"BRONZE_LEVEL\",\"animation_url\":\"https://enc-cbg.mypinata.cloud/ipfs/Qmaptgxi4gFAqHdaDX6dGj4NmyAiD3nc13uEDJm6PhZoqE\"}",
    "synced_at": "2022-03-17T16:53:17.403Z",
    "is_valid": 1,
    "syncing": 2,
    "frozen": 0
}
#12

and you try to resync the metadata for that specific token id 1 from 0xcdFea41c4A8e70Fb4838426069483dC50cbf5041 because it is not the correct one?

#13

The API works fine for tokens with id 1 to 670. Iā€™m having issues with tokens that have an id greater than 670. So Iā€™ve tried re-syncing number 671 with index.moralis.io/api/v2/nft/{address}/{id}/metadata/resync?chain=matic&flag=uri&mode=sync
So that would give https://deep-index.moralis.io/api/v2/nft/0xcdFea41c4A8e70Fb4838426069483dC50cbf5041/671/metadata/resync?chain=matic&flag=uri&mode=sync

Trying this will give the response { "status": "The metadata could not be updated! Try again later" }

The metadata / URI is form token 1 as the API to get the data isnā€™t working for 671, so I couldnā€™t get the data for that token.

#14

how do you know that token with id 671 exists?

#15

Hmm thatā€™s strange. I was testing my code and wanted to see if it would work on every key level (bronze, silver & gold). So I tested it on this silver key which according to the opensea details has an ID of 3926, which gave the response I mentioned before. I started doing some tests and found that the API only worked on IDā€™s smaller than 671.

From this Iā€™m guessing the ID mentioned on opensea and those used within the API arenā€™t the same?

#16

I donā€™t know what is with that ID, how did you create that NFT?

#17

I didnā€™t. Iā€™m building on top of it but there seem to be several issues with it.
Looks like Iā€™m either going to need to dig into the contract or contact the original devs :confused:

#18

Have you got solution about this? i faced same issue

#19

I faced this issue you have any solution about this?

#20

In need more info about your specific case. You can create a new forum post for it.