How to Handle NFT API Errors?

Written by

Published on October 1, 2024

While we work to ensure that every NFT's metadata is returned when requested from the API, there are various reasons why we may not able to fulfill your request.

📘 If present, errors in metadata fulfillment will appear in the error field of the response payload.

Below is a breakdown of the most common error types, how they occur, and how you should handle them.

Retryable Errors

These errors have a strong chance of being resolved with a repeated attempt:

Token URI responded with a non-200 response code
Throttled token URI
IPFS gateway timed out
Centralized gateway timed out (try again with a higher token URI timeout)
Arweave gateway timed out
Internal service error

You may retry requests with these errors as there’s a high probability of success on subsequent attempts.

Below are more detailed breakdowns of what many of our errors mean and how to approach them.

Token Does Not Exist

Was this article helpful?

Related FAQs

NFT API

How are NFTs Classified as “Spam” and Why?

Alchemy flags spam NFTs for ERC721 violations, honeypot mints and dishonest supply

NFT API

How Can I Update the NFTs Metadata Using Alchemy’s NFT API?

Quickly update NFT metadata with Alchemy’s invalidateContract and getNFTMetadata.

NFT API

How is the Floor Price Updated with getFloorPrice?

Discover how Alchemy’s getFloorPrice updates floor prices with caching and refresh intervals!

Not finding what you need?

Open a Support Ticket