Error: storing files: API Key is malformed or failed to parse.

Question

Error: storing files: API Key is malformed or failed to parse.

Closed this issue 4 months ago · 9 comments

I am trying to upload my NFTs to nft.storage but I keep received this error. I have purchased storage for this and it's worrying that I am unable to use it. Also the browser app does not allow to upload image files. It only accepts .csv which is quite weird. Please help me on this and kindly initiate a refund if it is not possible to help me on this.

Thanks!

Answer 1 · 2024-07-20T18:32:13.000Z

Hi! Thanks for reaching out

"API Key is malformed or failed to parse" is because
an API key from https://app.nft.storage/login
Is being used for
https://classic.nft.storage/ (the API, SDK or NFTUp).
API keys from https://app.nft.storage/login only work with https://app.nft.storage/login.

The original NFT.Storage product (now called NFT.Storage Classic) includes NFTUp.
To ensure the sustainability of our model, we're updating our service offerings no new uploads to the Classic product will be accepted as of 30 June 2024 at 5pm EST. The product in your screenshot is NFTUp.

For the new version which you've purchased storage for, first mint your NFTs then send us the NFT data—metadata and imagery CIDs, blockchain(s) minted on, contract address and token IDs. We preserve these in long term Filecoin storage. Note that you need to upload the data to IPFS separately, we recommend using Pinata or Lighthouse with our referral links to support NFT.Storage:
https://nft.storage/blog/announcing-our-new-partnerships-with-pinata-and-lighthouse

Answer 2 · 2024-07-21T05:39:51.000Z

that's insane! Can I get a refund on my purchase then - because I won't be needing 12gb just to store my metadata

Answer 3 · 2024-07-22T02:19:57.000Z

Please email ***@***.*** with refund requests.

…

On Sat, Jul 20, 2024, 11:40 PM Akaam-Zain ***@***.***> wrote: that's insane! Can I get a refund on my purchase then - because I won't be needing 12gb just to store my metadata — Reply to this email directly, view it on GitHub <#2726 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4YFHQJRBCTGXQPLUD23CW3ZNNCTZAVCNFSM6AAAAABLGD5NPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGQ4DGOJZGY> . You are receiving this because you commented.Message ID: <nftstorage/nft. ***@***.***>

Answer 4 · 2024-07-22T17:53:41.000Z

I do not see the email address - just *s. I have sent a request to support@nft.storage but have not heard anything yet.

Answer 5 · 2024-07-24T17:29:51.000Z

We will be in touch today. Thanks for your patience

…

On Mon, Jul 22, 2024, 6:54 PM Akaam-Zain ***@***.***> wrote: I do not see the email address - just *s. I have sent a request to ***@***.*** but have not heard anything yet. — Reply to this email directly, view it on GitHub <#2726 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4YFHQMFRGQDDYPS5NUURUDZNVBLXAVCNFSM6AAAAABLGD5NPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBTGUYDIOJSGI> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

Answer 6 · 2024-07-24T20:00:46.000Z

That is the correct email address. We have responded to all outstanding support requests. If you did not receive a response, please resend the email and also let me know here. We've been having some deliverability issues, thanks for your patience.

Answer 7 · 2024-07-25T04:42:09.000Z

sure I have forwarded the email again - please check and let me know. Thank you!

Answer 8 · 2024-07-25T17:00:49.000Z

My apologies, we have not received your email yet. We are experiencing email deliver ability issues, thanks for your patience. Since we are unable to connect via email, I wanted to let you know the storage that you purchased compliments hot storage solutions such as Pinata and Lighthouse.Storage, as the new version of NFT.Storage focuses on preserving the data in long term verifiable storage whereas the others listed focus on month to month hot storage. As we're a public good run by a small team, our policy is that storage isn't refundable, however I'd be happy to explain the value of NFT.Storage vs hot storage. I would also love to hear your feedback on the product so that we can improve it in the future. For the storage you bought, first mint your NFTs then send us the NFT data—metadata and imagery CIDs, blockchain(s) minted on, contract address and token IDs. We store these in long term Filecoin storage to preserve your NFT data. Note that you need to upload the data to IPFS separately, we recommend using Pinata or Lighthouse with our referral links to support NFT.Storage: https://nft.storage/blog/announcing-our-new-partnerships-with-pinata-and-lighthouse If you'd like to connect, here's my calendar to book a meeting: https://calendly.com/elizabeth_griffiths/30min Many thanks Elizabeth

…

On Thu, Jul 25, 2024, 5:42 AM Akaam-Zain ***@***.***> wrote: sure I have forwarded the email again - please check and let me know. Thank you! — Reply to this email directly, view it on GitHub <#2726 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4YFHQK6WUBM2EK4UPM7S4LZOB63NAVCNFSM6AAAAABLGD5NPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZGM3TMNBZHE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

Answer 9 · 2024-07-26T11:33:12.000Z

Closing this since we are now connecting for a meeting and also in email communication.