IPFS is a decentralized storage service FREE of use with Tatum.
IPFS does not require having files available on all reading gateways all the time.
Due to this, even with a valid CID
file, the endpoint Get file from IPFS may return the following:
{ "statusCode": 403, "errorCode": "ipfs.not.found", "message": "Unable to find file with cid QmYm5euqzeTCtaA1CVGqad7yy8jEijKzDCM8FurQ######." }
However, this does not mean that the file does not exist.
Good to know
NFTs can be minted with the CID
obtained from the endpoint Store data to IPFS even if you are unable to get 200 status from the endpoint Get file from IPFS.
Tatum's reading mechanism, depending on which gateway it connects to, might not be able to retrieve the data. Retrying the operation may hit a different gateway and should return the file.
Storing data in IPFS with alternative methods to Tatum's API endpoints may lead to desync issues with IPFS while attempting to mint NFTs.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article