# /nft/v2/{}/invalidateContract stops working

Calls to /nft/v2/{id}/invalidateContract on Alchemy API stopped working on September 30, 2026.

On September 30, 2026, the /nft/v2/{id}/invalidateContract endpoint was sunset to streamline and improve the NFT API. Requests sent to this endpoint fail since that day. This change affects all callers attempting to use the route on eth-mainnet.g.alchemy.com.

## What to use instead

Drop the call to /nft/v2/{}/invalidateContract. Instead, POST /nft/v3/{apiKey}/refreshNftMetadata remains available.

- 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
- Calls it hits: `/nft/v2/{id}/invalidateContract`
- Source: [Announcement](https://www.alchemy.com/docs/changelog)
- Verified: November 6, 2026, against Alchemy API's own pages
- Page: https://www.okapi.bot/providers/alchemy-api/breaking-changes/nft-v2-invalidatecontract-stops-working/

## 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 .

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent