Alchemy API
/nft/v3/{id}/getCollectionMetadata endpoint removal
Stopped workingSubscribe to Alchemy APIShare
On September 30, 2026, Alchemy removed the /nft/v3/{id}/getCollectionMetadata endpoint to streamline and improve the NFT API. Requests targeting this endpoint fail since that date.
Calls it hits
/nft/v3/{id}/getCollectionMetadata
What to use instead of these calls
Call GET /nft/v3/{apiKey}/getContractMetadata instead.
In Alchemy API's words
To streamline and improve the NFT API, Alchemy is sunsetting a small set of redundant endpoints — both their V2 and V3 versions — on September 30, 2026 .
Facts
- API
- Alchemy API
eth-mainnet.g.alchemy.com - Kind
- Endpoint removal
- Announced
- August 18, 2026
- Takes effect
- September 30, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Alchemy API's own pages
Questions
When does this change take effect?
Calls to /nft/v3/{id}/getCollectionMetadata on Alchemy API stopped working on September 30, 2026.
What happens to calls after September 30, 2026?
They have failed since September 30, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Alchemy API 10
-
/nft/v2/{id}/computeRarityEndpoint removal Stopped working -
/nft/v2/{id}/getCollectionMetadataEndpoint removal Stopped working -
/nft/v2/{id}/getCollectionsForOwnerEndpoint removal Stopped working -
/nft/v2/{id}/getNFTSalesEndpoint removal Stopped working -
/nft/v2/{id}/getSpamContractsEndpoint removal Stopped working -
/nft/v2/{id}/invalidateContractEndpoint removal Stopped working -
/nft/v2/{id}/isAirdropEndpoint removal Stopped working -
/nft/v2/{id}/isHolderOfCollectionEndpoint removal Stopped working -
/nft/v2/{id}/searchContractMetadataEndpoint removal Stopped working -
/nft/v2/{id}/summarizeNftAttributesEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.