Starting on March 17, 2023 we no longer support existing and new accounts on Crypto.org. We have communicated this over email to impacted teams, and are adding here for posterity.
We have added
indexed as a block tag param for alchemy_getAssetTransfers. This block tag can be used instead of
latest as the
toBlock param. Under normal circumstances,
indexed will have the same behavior as
latest. However, under certain unusual situations such as a network fork or partial network outage, transfers data up to the
latest block may not be available. In these cases, if
latest is used as the
toBlock, we will return an error; however with
indexed, we will instead try to return whatever transfers data is available.
NFT Activity Webhooks are now supported on Polygon, Arbitrum, and Optimism mainnet and testnets.
We are excited to release
alchemy_simulateExecution. More below. 🎉
We are very excited about Unstoppable Domains and the future of digital identities, but Unstoppable Domains is in the process of taking support for these APIs in-house. This is exciting news for all UD customers as it will allow for greater API flexibility and new features; but as part of that transition we will be deprecating Alchemy support for UD endpoints. For more information about how to use the Unstoppable Resolution Service API service, please visit the Unstoppable Domains developer hub.
Starting on November 8, 2022 we no longer support existing and new accounts on Flow. We have communicated this over email to impacted teams, and adding here for posterity. We recommend using the Flow’s public access api. For Flow NFT API’s the Flow team recommends the following options:
We are adding wildcards for NFT Transfer Activity webhooks and moving to per block delivery.
The NFT API has a new getNFTMetadataBatch endpoint to conveniently fetch NFT metadata for a list of NFTs. Unlike other NFT API methods, this is a POST method that takes a list of tokens in the request body.
includeFilters parameter has been added to the getNFTs API. When
includeFilters are set, only NFTs that match one of the specified filters will be included in the result. For clarity, the existing
filters param has been renamed to
excludeFilters (note: this is NOT a breaking change, as the
filters param will continue to be supported).
excludeFilters are mutually exclusive, and specifying both types of filters will result in an error.