Read all subfolders and requests under collection

I am able to read all the subfolders and requests under collection using https://api.getpostman.com/collections/ for a small collection with 10-20 api requests. But when i try the same with large collection which has 2000+ requests, it’s getting timed out. Is there any limitation on the number of requests under collection for this getpostman api?

Any update on the above?

Hey @joint-operations-phy :waving_hand:

You mentioned “read all the subfolders and requests”, could you share a bit more about how you’re doing that? For example, are you working directly in the Postman UI, or are you using the Postman API from another platform?

Also, do you happen to know the approximate file size of the Collection?

It would be great to understand a bit more about your setup and the use case behind having 2000+ requests in a single Collection, that context will really help us pinpoint what might be happening.

Thanks @danny-dainton for your response. Please find below the details

Our postman collection hierarchy is maintained like below. It’s maintained something like ////.

I am using the postman provided api to get the collection details but it’s getting timed out.

https://api.getpostman.com/collections/collectionid?apikey=apikey

I tried to export the collection to get the file size of the collection but it’s throwing the error. Tried multiple times but it’s the same issue. Not sure what’s the limitation to export the collection.

Here is an example where the getpostman api worked which has 124 requests, but similar kind of folder hierarchy

The intention is to programmatically fetch the postman collection and navigate through the folders and requests by specifying the collection name and the folder hierarchy from ci/cd pipeline.

Hope it covers all the information needed to understand our use case.

Appreciate the additional information here :folded_hands:

You have your contextual reasons for structuring your Collections in this way but there seems to be a lot of repetition here:

It feels like each release could be its own Collection. :sweat_smile:

I’ll reach out to the Postman API team to check if there are any size limitation and any timeout limits on returning a response.

Are you able to get a response when you use the ?model=minimal param?

Yeah, we understand that the current folder structure is not the right way to maintain a collection. We will be eliminating the duplicates with in the collection and we are in the process of coming up with a new proposal for the collection folder structure and how it needs to be maintained. In order to come up with the new recommendation, we wanted to understand the limitations on the collection’s folder structure as well as the number of request limit in the collection so that we can maintain it properly in the future. Hoping for a quick turn around on the response from the Postman API team. Thanks for understanding the problem statement and working with the respective team for the resolution.

I tried with the params suggested, but it’s still the same issue.

@danny-dainton - Any update on the above ?