getNftsForContract totally broken about alchemy-sdk-js

[thestriver]

Hi @S1nPur1ty,

Are you still facing this issue?
I think there has been a mixup due to the renaming of getNFTsForCollection to getNftsForContract on alchemy-sdk. That's been mentioned in the docs now.

If you try Alchemy's composer tool getNFTsForCollection function and the curl request getNFTsForCollection:https://docs.alchemy.com/reference/getnftsforcollection without specifying metadata as true, it will only return the token ids of the specified collection address.

curl --request GET \
     --url 'https://eth-mainnet.g.alchemy.com/nft/v2/docs-demo/getNFTsForCollection?contractAddress=0xe785E82358879F061BC3dcAC6f0444462D4b5330&withMetadata=true' \
     --header 'accept: application/json'

Whereas with the equivalent alchemy-sdk getNftsForContract, all the information, including metadata, is returned at the same time.

I hope this answers your issue.

[thebrianchen]

@thestriver Thanks for answering the question. The SDK has renamed some of the API names, but the next version of the NFT API endpoints will bring the naming conventions back to the same standard. I'm going to close this issue since it's working as intended, but feel free to ask any other questions you may have!