Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
[X] I have searched the existing issues for this feature request and I know that duplicates will be closed
Is your feature request related to a problem?
We publish our API documentation based on our Postman collection. In addition to adding new folders and requests, we often move existing folders and requests to improve readability. Because of the difficulty of identifying changes, the most convenient method to update has been to use Replace a collection's data and let Postman sort out the merge.
When the file size approaches 10 to 12 MB, Postman often returns the error: "Request body size limit exceeded," or the gateway returns 504 Gateway Timeout errors.
Describe the solution you'd like
The documentation for Replace a collection's data states:
The maximum collection size this endpoint accepts cannot exceed 20 MB.
Postman routinely fails as the file approaches 10 MB and always fails when the file approaches 12 MB (I submitted a bug). However, even if Postman fixes the bug, our product continues to add features and the Postman collection grows. At some point, it will exceed the 20 MB limit.
Permit Replace a collection's data to accept Content-Type: application/octet-stream for for collections greater than 20 MB.
Describe alternatives you've considered
I tried to remove all .body keys and then update them individually, but Update a response does not update .body. I tried to remove .item[] keys and then update them individually, but Update a folder does not update .item[].
In theory, I could diff the JSON, but even if I made the hundreds of calls to update the changes, example responses would remain useless because .body keys cannot be updated.
Is there an existing request for this feature?
Is your feature request related to a problem?
We publish our API documentation based on our Postman collection. In addition to adding new folders and requests, we often move existing folders and requests to improve readability. Because of the difficulty of identifying changes, the most convenient method to update has been to use Replace a collection's data and let Postman sort out the merge.
When the file size approaches 10 to 12 MB, Postman often returns the error: "Request body size limit exceeded," or the gateway returns 504 Gateway Timeout errors.
Describe the solution you'd like
The documentation for Replace a collection's data states:
Postman routinely fails as the file approaches 10 MB and always fails when the file approaches 12 MB (I submitted a bug). However, even if Postman fixes the bug, our product continues to add features and the Postman collection grows. At some point, it will exceed the 20 MB limit.
Permit Replace a collection's data to accept
Content-Type: application/octet-streamfor for collections greater than 20 MB.Describe alternatives you've considered
I tried to remove all .body keys and then update them individually, but Update a response does not update .body. I tried to remove .item[] keys and then update them individually, but Update a folder does not update .item[].
In theory, I could diff the JSON, but even if I made the hundreds of calls to update the changes, example responses would remain useless because .body keys cannot be updated.
Additional context
No response