Add ability to request for a restricted set of fields when listing files

[Freezystem]

Is there a way to limit returned fields in the list request ?

It would be a nice thing to be able to limit the returned fields to reduce bandwidth, memory usage and increase overall performances.

For instance, we're sometimes listing files just to get their id in order to move them to a different group or delete them. I don't need anything but the id field in that case and there is a lot of useless information transiting through the network.

This could be done through a dedicated query parameter taking a comma separated list of fields like: https://api.pinata.cloud/v3/v3/files/public?fields=id,cid,name.

Regards,

[stevedylandev]

Hey there! This isn't currently possible but I love the idea! Will shoot it over to our team as a feature request.

Few quick questions:

• How many files are you getting returned? Curious as to how much extra data is being returned
• Are you utilizing filtering by group / no-group?

Appreciate the feedback!

[Freezystem]

Actually I was transferring old files created without groups to their respecting one based on their metadata key.

e.g: getting all files id with {env: "dev"} metadata to put them in the dev group.

So I was sometimes getting like a 1000+ files at once.

Another interesting feedback:
As we are using groups to split our files by their environment of origin, it would be awesome to be able to generate an API key scoped to a group to avoid collisions.
We would be able to delete all files from our "dev" group on regular basis without the fear of deleting files from "prod" group by error (as group uuids are easy to invert).
We are fine with the group logic and would prefer not to have to create a pinata account per environment.

[stevedylandev]

Good to know, thank you!! 🙏 Having a way to designed and scope environments is also something we'll be looking into. I'll keep you posted on the original request.