Menu
We are thinking of using a REST interface for communication between internal apps. App A will have to pass a fair bit of data representing a financial portfolio to app B. Is there any limit to the amount of data that can be passed using a REST API given that REST is implemented using HTTP? I wasn't sure if another protocol (ie: RMI) should be used with a large data set.
326
Endpoint-Specific Limits The maximum data payload size for requests to this endpoint is 128 mb. The maximum rate limit is 60 files per hour per account (aka profile).
The limit on the payload size of a POST request is defined by configuration. The default configuration for the limit in Apigee Edge (Cloud) is 10 MB. The default configuration for an OPDK installation is 3 MB. The limit on the payload size of a POST request is defined by configuration.
One of the disadvantages of RESTful APIs is that you can lose the ability to maintain state in REST, such as within sessions. It can also be more difficult for newer developers to use. It's important to understand what makes a REST API RESTful, and why these constraints exist before building your API.
API Routes Response Size Limited to 4MB API Routes are meant to respond quickly and are not intended to support responding with large amounts of data. The maximum size of responses is 4MB.
No, it's pretty much up to the server implementation if there's any such limit.
There's a limit on the size of a URL (if you wish to put large amounts of data on the URL, like with a GET), but no defined limit for a POST or PUT.
154
As Will Hartung said, there is no limit in the standard (RFC 2616). But every implementation has its own limits. A few examples:
post_max_size)These implementation limits are usually just the default configuration values, and can be changed to larger ones if required.
35
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
