Okapi Okapi
Add to GitHub

Alchemy API · eth-mainnet.g.alchemy.com

Alchemy API v3 deprecations

The breaking changes Alchemy API announced for its v3 endpoints: 10 of the 20 Okapi tracks.

Already in effect 10

  1. /nft/v3/{id}/computeRarityEndpoint removal Stopped working
  2. /nft/v3/{id}/getCollectionMetadataEndpoint removal Stopped working
  3. /nft/v3/{id}/getCollectionsForOwnerEndpoint removal Stopped working
  4. /nft/v3/{id}/getNFTSalesEndpoint removal Stopped working
  5. /nft/v3/{id}/getSpamContractsEndpoint removal Stopped working
  6. /nft/v3/{id}/invalidateContractEndpoint removal Stopped working
  7. /nft/v3/{id}/isAirdropNFTEndpoint removal Stopped working
  8. /nft/v3/{id}/isHolderOfContractEndpoint removal Stopped working
  9. /nft/v3/{id}/searchContractMetadataEndpoint removal Stopped working
  10. /nft/v3/{id}/summarizeNFTAttributesEndpoint removal Stopped working

Questions

Is the Alchemy API v3 deprecated?

Alchemy API has announced 10 breaking changes to its v3 endpoints: 10 with a shutdown date. Each one's page says what to use instead.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls these changes hit and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Know before your API calls break.

Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.

Add to GitHub