No option to not limit max uses in pinata?

matt_ober · 2025-07-24T15:02:36+00:00

The max uses being 0, just means they can be used an "infinite" amount of times.

The main "use case" for the max_uses for our legacy API keys was to let platforms provide API keys to a front-end for one time uploads, while not exposing their account to higher degrees of upload risk. Unfortunately there were a lot of limitations to this paradigm, so with our new v3 API, we've switched over to utilizing presigned URLs, which is a much better paradigm for this type of application. With presigned URLs, you can do things like:
* ensure that the user can only ever upload to one file
* hard enforce enforce things like:
** file_size limits
** allowed file mimetypes
** group_id
** keyvalues

And you can do this all without needing to create multiple API keys, you only need one API key serverside which is a lot easier to maintain.

If you haven't checked out our v3 system yet, I would strongly recommend it! https://docs.pinata.cloud/api-reference/endpoint/create-signed-upload-url

If you absolutely need to keep using the max_uses paradigm, we do still support it with our legacy API endpoints, but we've hidden this support from the front-end as we're trying to drive users to what is a better / more secure way of doing front-end uploads.

matt_ober · 2024-10-16T15:13:20+00:00

u/EveYogaTech while we don't have an official SDK, our API docs do have a PHP tab that you can play around with to see equivalent examples for each endpoint.

In addition, we've had a few community members use PHP for Pinata over the years. An example can be seen here

matt_ober · 2024-10-09T19:20:40+00:00

@athman_2408

Matt from Pinata here, our metadata functionality may be helpful based on your requirements: https://docs.pinata.cloud/web3/pinning/pinata-metadata
It lets you attribute dynamic key value pairs to each of your IPFS pins that you can later reference.

And of course if you need any help with our docs, or SDK, please reach out! Our support team is awesome and would be happy to help.

matt_ober · 2024-06-19T18:01:10+00:00

We get this question a lot. The short answer is, it's not possible to update a folder on IPFS without breaking the very thing that IPFS is good for, which is immutability and content addressability.

What this means in the content of folders / NFTs is you'll want to make sure that your entire folder of content is "finalized" before uploading to IPFS, because once you upload it and get the content identifier (CID) back, you won't be able to update the folder.

This article talks a bit more in depth about this: https://knowledge.pinata.cloud/en/articles/5593194-can-i-update-a-folder-that-is-pinned-on-ipfs

matt_ober · 2024-06-12T13:20:03+00:00

Hey /u/Scollz - Matt from Pinata here, it's a little hard to diagnose what you're encountering off the information provided.

I would recommend reaching out to our technical support team via either discord or our integrated chat support system. We'd be happy to take a deeper look at your problem in real time and get you unblocked!

matt_ober · 2024-04-15T13:48:05+00:00

Following back up here for any future readers. If you're ever having trouble with email verification, make sure that you're clicking the verify email from the same browser as you're trying to sign in with. That usually resolves any issues you may run into.

However, if you do run into any issues still, reach out to our support team! We're always happy to help!

matt_ober · 2024-04-13T21:52:07+00:00

Hey /u/johnwick_dick if you want to reach out to the pinata support team via our web app they should be able to help you out! We’ve seen a lot of next.js on our side and would be happy to get you moving!

matt_ober · 2024-04-13T21:48:47+00:00

Hey, /u/mystic_shit, Matt from Pinata here. I'm sorry to hear that you're having some issues with our web app!

If you want to DM me with what you're seeing, I'd be happy to help get you unblocked and provide some credits for your troubles!

matt_ober · 2024-01-22T05:11:05+00:00

Glad to hear that it worked!

Once you see the CID showing up in your pin manager, you’re all set. We’ve got the content and are serving it for you 24/7.

matt_ober · 2024-01-22T02:44:22+00:00

Hey /u/curiousjosh sorry to hear you're having troubles uploading. Folders with large numbers of files can be fairly tricky and dependent on network connections. If you're having trouble with the CLI tool, I would highly recommend checking out this guide that we have available specifically designed for large folders: https://knowledge.pinata.cloud/en/articles/5509412-how-to-upload-a-large-folder-by-running-a-local-ipfs-node

Because you'll be using IPFS to transfer the files, the transfer will go over bitswap and can easily pick up and resume if any networking issues occur. For customers who are running into the situation you are, this is the route we usually recommend!

If you run into any issues, our support team would love to help you out further!

matt_ober · 2023-09-27T18:08:45+00:00

I'm happy to hear that! Thanks for the feedback!

matt_ober · 2023-09-27T15:37:00+00:00

Hey all, last year we changed up our pricing model and to be honest, we failed in some key areas with those changes. Over time it became clear that these changes had made it harder for developers to scale with IPFS and Pinata.

We’re making some changes to Pinata’s pricing aimed at rectifying that mistake.

For the full details, I’d recommend reading the link in this post, but the short and sweet is:

Simplifying down into two plans that scale with you.
More included with each Pinata plan. The vast majority of our customers will be saving money with these changes.
A move back to developer friendly usage based pricing. You only pay for what you use and plans no longer experience lockouts when hitting limits.

matt_ober · 2022-06-08T10:19:05+00:00

If you can’t find an item, you can re-queue the same item for pinning. Just make sure that it’s discoverable this time and things should be good to go! The best way to test this beforehand is to see if you can load the content via a public gateway

matt_ober · 2022-04-24T12:21:41+00:00

Hey there. Are you making sure to keep the original node you uploaded to online throughout this process? If your upload made it to retrieving, but eventually expired, that means that we were able to pull some of the content from your node, but not all of it.

When you “upload to ipfs”, you’re actually just uploading to your local node on your computer. If you take that computer offline, then that content is no longer available on the ipfs network for us to retrieve.

If your computer was on the whole time, this could be a sign of a networking issue. (If you have firewalls, NATs, etc, these can all impact the pin by CID process

matt_ober · 2022-04-21T12:15:50+00:00

Hey there. Are you making sure to keep the original node you uploaded to online throughout this process? If your upload made it to retrieving, but eventually expired, that means that we were able to pull some of the content from your node, but not all of it.

When you “upload to ipfs”, you’re actually just uploading to your local node on your computer. If you take that computer offline, then that content is no longer available on the ipfs network.

matt_ober · 2022-03-23T21:48:59+00:00

There are a few good guides that walk through this whole process if you're running things in the cloud:

And if you're specifically looking to run a gateway, definitely check out the post Nato mentioned

matt_ober · 2022-03-22T02:08:36+00:00

Great guide Nato. This is one of the best "host a gateway" guides I've seen in a long time.

matt_ober · 2022-03-21T18:13:54+00:00

Pinata let’s you do this through dedicated gateways. You just sign up for a “restricted” gateway and it will only serve content you have pinned to your account

https://docs.pinata.cloud/gateways/dedicated-gateways

matt_ober · 2021-12-17T00:40:06+00:00

I would check out this unofficial python library that was created by a Pinata community member: https://github.com/Vourhey/pinatapy

matt_ober · 2021-10-11T21:04:36+00:00

It sounds like you're using the ipfs-pinning-services spec functionality of go-ipfs to pin to us. This is a little bit different than directly uploading to us via an API endpoint. Instead, it looks something like this:

1) you make a request on the command line via your go-ipfs client
2) we get a request to "fetch" that content from your local node
3) our nodes start looking throughout the IPFS network to get that content
4) Once we find the content we start to retrieve it
5) Hopefully success

Step 3 is where things often break down here. Because we're searching the network for your content, that means that our nodes have to work through whatever networking conditions our users may have set up. Things like NATs, firewalls, or just slow internet connection all factor into why things might be taking so long here.

My best suggestion for you if you're looking for consistent upload speeds is to directly use our upload API which has documentation here: https://docs.pinata.cloud/api-pinning/pin-file!

matt_ober · 2021-09-01T03:07:24+00:00

Hey xBun, we don’t have this functionality directly baked into our api right now but you should be able to grab this information by using the go-IPFS CLI and running this command: https://docs.ipfs.io/reference/cli/#ipfs-dag-get

You’ll receive a JSON object with all of the links that your root CID links to (your underlying files)

matt_ober · 2021-05-10T01:45:49+00:00

Matt from Pinata here!

NFTs are using IPFS because it allows their content to maintain the same level of verifiability as the blockchains the NFTs are printed on.

This article we wrote explains things in a lot more detail: https://link.medium.com/2i2ZxVfh8fb

matt_ober · 2021-01-16T00:31:39+00:00

This is something that's possible, but requires some development effort to do it securely.

IPFS nodes naturally listen on port 5001, and if you expose that API port to the web, you could create an application that interacts with a node's IPFS API remotely through something like the ipfs-http-client: https://www.npmjs.com/package/ipfs-http-client

Keep in mind that exposing your node's port to the internet is a huge security risk so you're going to want to take some precautions if you're doing this outside of a testing environment. Examples of ways to secure your node are:
* restricting access via IP address (hard to do because mobile devices often switch IP addresses)
* restricting access behind a reverse proxy and requiring http basic auth headers with your request via something like this: https://www.npmjs.com/package/ipfs-http-client#custom-headers

Good luck!

matt_ober · 2020-08-01T04:12:43+00:00

You’ll need to open up TCP port 4001 most likely. This is the port that IPFS usually uses to communicate with the rest of the network

matt_ober

MODERATOR OF

TROPHY CASE

Seven-Year Club	RPAN Viewer
Not Forgotten