---
title: "How to handle NFT API errors?"
description: "Learn about common NFT API errors, their causes and solutions for smoother integration!"
---

# How to handle NFT API errors?

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.

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

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:

1. **Token URI responded with a non-200 response code**
1. **Throttled token URI**
1. **IPFS gateway timed out**
1. **Centralized gateway timed out \(try again with a higher token URI timeout\)**
1. **Arweave gateway timed out**
1. **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