Open chopperdaddy opened 3 years ago
When making a requests to the /nft/{address} endpoint, I'm often getting null metadata in some of the token objects in the "result" array.
I'm able to reproduce this issue with many contract addresses but here's an example:
curl -X 'GET' \ 'https://deep-index.moralis.io/api/v2/nft/0x2acAb3DEa77832C09420663b0E1cB386031bA17B?chain=eth&format=decimal&order=DESC' \ -H 'accept: application/json' \ -H 'X-API-Key: [API KEY]'
returns
"result": [ {...} { "token_address": "0x2acab3dea77832c09420663b0e1cb386031ba17b", "token_id": "9996", "contract_type": "ERC721", "token_uri": "https://api.deadfellaz.io/traits/9996", "metadata": null, "synced_at": null, "amount": "1", "name": "DeadFellaz", "symbol": "DEADFELLAZ" }, {...} ]
Same problem here.
I have same contract on BSC and BSC Testnet and on testnet I receive the metadata and on the main no.
When making a requests to the /nft/{address} endpoint, I'm often getting null metadata in some of the token objects in the "result" array.
I'm able to reproduce this issue with many contract addresses but here's an example:
curl -X 'GET' \ 'https://deep-index.moralis.io/api/v2/nft/0x2acAb3DEa77832C09420663b0E1cB386031bA17B?chain=eth&format=decimal&order=DESC' \ -H 'accept: application/json' \ -H 'X-API-Key: [API KEY]'
returns
"result": [ {...} { "token_address": "0x2acab3dea77832c09420663b0e1cb386031ba17b", "token_id": "9996", "contract_type": "ERC721", "token_uri": "https://api.deadfellaz.io/traits/9996", "metadata": null, "synced_at": null, "amount": "1", "name": "DeadFellaz", "symbol": "DEADFELLAZ" }, {...} ]